Bronnen · 23
Prioriteer kwetsbaarheden en verifieer de herstelmaatregelen
Verbind bekende exploitatie, blootgestelde assets, zakelijke impact en bewijs van een werkende oplossing.
Bijgewerkt · 9 min
Wat deze handleiding helpt bereiken
- Koppel waarschuwingen aan assets
- Rangschik de werkelijke urgentie
- Veilig uitrollen
- Verifiëren en afsluiten
Snelle controle
- Is het getroffen product en de getroffen versie daadwerkelijk geïmplementeerd?
- Is de asset bereikbaar en bedrijfskritisch?
- Is de exploitatie gedocumenteerd?
- Wat beschermt de service vóór een patch?
- Bevestigt een controle dat het probleem is verdwenen van de asset?
Stapsgewijze methode
- 1
Consolideer de inventaris
Breng services, producten, versies, omgevingen, blootstelling en eigenaren in kaart. Een componentadvies alleen bewijst niet dat een kwetsbare instantie is geïmplementeerd.
Resultaat: gedateerde lijst van getroffen assets en onzekerheden.
- 2
Kwalificeer de bevinding
Vergelijk het advies van de leverancier, de CVE-identificatiecode, de exploitatievoorwaarden en, indien relevant, de CISA-catalogus van bekende misbruikte kwetsbaarheden. Noteer wanneer elke bron is gecontroleerd.
Resultaat: bevinding met primaire referenties.
- 3
Stel een verdedigbare prioriteit vast
Houd rekening met bekende exploitatie, bereikbaarheid van assets, vereiste privileges, verwerkte gegevens, impact op de service en beschikbare herstelmaatregelen. Wijs een verantwoordelijke en een contextspecifieke deadline toe.
Resultaat: gemotiveerde prioriteitsbeslissing.
- 4
Bereid de wijziging voor
Breng afhankelijkheden, wijzigingsvenster, back-up en terugdraaien in kaart. Als een update niet direct kan worden toegepast, noteer dan de tijdelijke controle en de vervaldatum ervan.
Resultaat: uitrolplan en beperkte uitzondering.
- 5
Implementeer en test
Pas de oplossing of mitigatie van de leverancier toe met behulp van het goedgekeurde proces. Controleer de resulterende versie, het bedrijfsproces en de integraties die mogelijk problemen veroorzaken.
Resultaat: implementatieverslag en functioneel resultaat.
- 6
Controleer de afsluiting.
Controleer de daadwerkelijke asset met een geschikte methode, vind gemiste gevallen en herzie uitzonderingen. Sluit een ticket niet af omdat er slechts een update is ingepland.
Resultaat: verificatiebewijs en bijgewerkt register.
Managementindicatoren
| Indicator | Wat het meet | Eerste actie |
|---|---|---|
| Dekking | Kritieke assets met bekende versies en eigenaren | Voltooi de inventaris |
| Vertraging | Tijd tussen kwalificatie en geverifieerde oplossing | Verwijder terugkerende knelpunten |
| Verificatie | Oplossingen opnieuw getest op echte assets | Heropen sluitingen zonder bewijs |
| Uitzonderingen | Vrijstellingen met beheer, eigenaar en vervaldatum | Sluit verlopen uitzonderingen |
Veelvoorkomende fouten
- Rangschikking uitsluitend op basis van een generieke score zonder de asset te controleren
- Ervan uitgaan dat een KEV-lijst betekent dat het product in uw omgeving aanwezig is
- Implementatie zonder het servicegedrag te testen
- Compenserende controles laten staan zonder een beoordelingsdatum
Veelgestelde vragen
Moet de CVE met de hoogste score altijd als eerste worden aangepakt?
Een score beschrijft de technische ernst; bekende exploitatie, blootstelling en lokale service-impact bepalen uw operationele volgorde.
Wat als er geen patch bestaat?
Volg de maatregelen van de leverancier, beperk de blootstelling waar mogelijk en documenteer een verantwoordelijke, een beoordelingsdatum en het resterende risico.
Wanneer is het werk afgerond?
Nadat de versie of maatregel is geverifieerd op de getroffen instanties en de kritieke functionaliteit is getest.
Referenties: gegevens, gebruik en grenzen
Documentatie geraadpleegd op .
De uitgebreide toelichtingen zijn in deze editie beschikbaar in het Engels.
| Bron en doel | Gecontroleerde gegevens of maatstaf | Praktisch gebruik | Te behouden beperking |
|---|---|---|---|
| FIRST · CVSS Describe technical vulnerability severity using an explicit method and vector. |
CVSS 4.0 scores run from 0.0 to 10.0. Base, Threat, Environmental and Supplemental metric groups serve different purposes. | Retain the score version, vector and date. Compare it with the installed version, access paths and business consequences before ordering remediation. | A high score is not evidence of exploitation; a low score does not mean a service has no risk. |
| FIRST · EPSS Estimate exploitation probability for a published CVE. |
The model looks ahead 30 days. Its score is a probability; its percentile ranks that score relative to other CVEs. | Record the data date and distinguish probability from percentile. Add asset exposure and confirmed exploitation evidence. | The model does not predict harm to your organisation. Low probability does not cancel a critical exposure. |
| CISA · Known Exploited Vulnerabilities Identify vulnerabilities listed by CISA as known to be exploited. |
The catalogue includes CVE, product, date added and required action. Its official repository also provides the data schema. | Check applicability to your products and retain the access date. Review the requested action and vendor advisory before confirming remediation. | Absence from the catalogue does not establish safety. Administrative deadlines in it are not automatically binding on every organisation. |
CVSS, EPSS, KEV en VEX
De uitgebreide toelichtingen zijn in deze editie beschikbaar in het Engels.
Vulnerability prioritisation: four signals to connect to the asset
A vulnerability queue often mixes information answering different questions. CVSS describes technical severity, EPSS estimates a probability of observed exploitation, KEV records known exploitation and VEX carries a product applicability assertion. A local decision still needs the deployed version, access paths and consequences of exploitation.
These are documentary reference points. EPSS examples, situations and the VEX product are fictional; no current CVE score, real inventory or scan result is presented. This page calculates neither CVSS, organisational risk nor an automatic priority. Proposed evidence and decisions are a local editorial method.
Four independent panels: CVSS describes severity; EPSS estimates observed exploitation within thirty days; KEV records known exploitation; VEX states declared applicability. Compare them with the deployed product and its context without adding them into one score.
Four questions and four kinds of information
| Source | Useful question | What it cannot establish alone |
|---|---|---|
| CVSS 4.0 | What is the technical severity under the assessed metrics? | The score proves neither exploitation nor consequences for your service. |
| EPSS | What is the estimated probability of observing exploitation of this CVE in the next thirty days? | It does not describe compromise of your instance, its controls or business loss. |
| CISA KEV | Is the vulnerability listed as known to be exploited? | Listing does not establish that the product exists in your estate; absence does not establish safety. |
| VEX | What does an issuer assert about a vulnerability for identified products at a stated time? | An assertion alone proves neither deployment of the relevant version nor issuer trustworthiness. |
CVSS 4.0: preserve groups, vector and assessment author
A number from 0 to 10 loses meaning when its version, vector and assessed groups disappear. FIRST distinguishes CVSS-B, CVSS-BT, CVSS-BE and CVSS-BTE. Undefined Threat and Environmental metrics take default values rather than disappearing from the calculation.
| Group | Role | Reading check |
|---|---|---|
| Base | Intrinsic vulnerability characteristics. | A supplier’s CVSS-B is not your priority decision. |
| Threat | Threat characteristics that can change over time. | Date the assessment and explain exploitation information used. |
| Environmental | Characteristics specific to the consumer’s environment. | State the controls and system importance considered rather than silently changing a score. |
| Supplemental | Additional context, such as Safety or Recovery. | These metrics do not modify the final CVSS score; they may inform a separate local analysis. |
EPSS: probability, percentile and missing data
FIRST describes a probability from 0 to 1, updated daily, over a thirty-day horizon. The percentile is a relative rank among currently scored vulnerabilities. Do not add probability and percentile or turn their pair into the probability of an attack on your organisation.
| Fictional example | Provided values | Correct reading |
|---|---|---|
| A probability | Probability : 0.05 · Percentile : Unspecified | 0.05 means a 5% estimated probability of observed exploitation within the model horizon, rather than an estate compromise rate. |
| Probability and rank | Probability : 0.02 · Percentile : 0.97 | In this fictional example 0.02 means 2%, while 0.97 places the score at the 97th percentile. The rank does not turn a 2% probability into 97%. |
| No received value | Probability : Unspecified · Percentile : Unspecified | Missing data remains unknown; it is neither zero nor evidence of no exploitation. Record the failure or the date of the last available value. |
Seven useful readings of the KEV schema
The official CISA repository schema describes the catalogue and its entries. The following selection helps retain consultation context rather than enumerate every field. Match each entry to the supplier advisory and actual asset.
| Fields | Meaning | Proposed check |
|---|---|---|
| catalogVersion / dateReleased | Catalogue version and publication time. | Keep a reference to the consulted edition; distinguish publication time from your assessment time. |
| cveID / vendorProject / product | Identifier and product associated with the entry. | Match name, version, distribution and embedded components before declaring an asset affected. |
| dateAdded | Date the vulnerability entered the catalogue. | Do not present it as the first exploitation date or CVE publication date. |
| requiredAction | Requested action to address the vulnerability. | Read the complete instruction and supplier references, then document local implementation. |
| dueDate | Catalogue deadline for the requested action. | Check the context and scope of the CISA instruction before adopting it as a local deadline. |
| knownRansomwareCampaignUse | Known indicates confirmed ransomware campaign use; Unknown means CISA lacks confirmation. | Do not translate Unknown into never used or a definite false value. |
| cwes | Weakness category codes associated with the entry. | Use categories to group causes; they do not replace the CVE identifier or affected version. |
Six fictional situations: what is missing before a decision?
High severity, product not located
An advisory reports high severity; the inventory cannot locate that version in the estate.
Confirm presence and version with the owner, including embedded dependencies.
Retain applicability unknown. Absence from an incomplete inventory does not justify closure.
Known exploitation, exposed instance
The vulnerability is listed as known to be exploited and an owner confirms an affected internet-accessible instance.
Review supplier actions and arrange exposure reduction and remediation suited to the service.
Name the owner, interim control and expected verification evidence; a severity score alone supplies none of this traceability.
Low probability, essential service
The fictional EPSS probability is low, but the affected instance supports an essential service.
Assess consequences and access paths before agreeing a change window.
Do not treat a low score as insurance; that instance’s controls are not contextual inputs to EPSS.
VEX for another version
The supplier declares version 2.4.0 not affected; the asset still runs 2.3.0.
Seek an assertion applicable to the installed version and verify its provenance.
Do not extend a conclusion across versions. A VEX document deploys no update.
Temporary control becomes permanent
A temporary rule reduces access; its review date has passed.
Check that it still protects the relevant path, then decide whether to maintain it or apply the fix.
Keep the owner, limits and a new review date. A perimeter control is not automatically an OpenVEX built-in product mitigation.
Patch announced, deployment unverified
A fixed release is available, but the ticket contains only a download link.
Check the version actually deployed, remaining instances and critical functionality.
Close on implementation and verification evidence, rather than the supplier’s availability of a patch.
Eight records for a traceable remediation decision
- Product, version or build, environment and asset owner.
- Vulnerability identifier, supplier advisory and relevant exploitation conditions.
- CVSS version, vector, metric-group nomenclature and assessment author.
- EPSS date, probability and percentile in separate fields, or an explicit missing value.
- Dated KEV status, requested action and consulted catalogue edition.
- Applicable VEX assertion: issuer, product, version, time and any justification.
- Reasoned local decision, interim control, owner and review date.
- Deployment or mitigation evidence, verification result and remaining limits.
Read VEX statuses and applicability conditions →
Primary sources and scope
- FIRST · CVSS 4.0 Specification · CVSS 4.0 · document 1.2 · reviewed 2026-10-22
Overview · Assessment · Nomenclature · Supplemental Metrics - FIRST · EPSS Frequently Asked Questions · Living FAQ · reviewed 2026-10-22
What is EPSS? · Reading the score · Percentile · Score changes - CISA · KEV official data schema · Official CISA mirror · reviewed 2026-10-22
Catalog properties · vulnerability properties · required fields - OpenVEX · Specification v0.2.0 · OpenVEX v0.2.0 · reviewed 2026-10-22
Statement Data Structure · Status Labels · Status Justifications · Data Inheritance
Sources checked on
Buildhandtekening en herkomst
De uitgebreide toelichtingen zijn in deze editie beschikbaar in het Engels.
Verify patch origin and then its application
A fixed version needs connecting to the received package and updated instance. Provenance verification helps establish expected origin; remediation confirmation still requires checking the active version and relevant behaviour.
- Keep the accepted patch digest and signature/provenance verification results.
- Match that package to the version actually deployed on each targeted instance.
- Do not close on authenticity alone: document remediation checks, regressions and remaining limits.
Read the pre-deployment provenance reference →
Sources checked on · SLSA 1.2 · Build: Verifying artifacts · SLSA 1.2 · Build: Provenance · SLSA 1.2 · Build: Track Basics · in-toto · Statement v1 · Sigstore · Verifying Signatures
De CISA KEV-catalogus verkennen
De uitgebreide toelichtingen zijn in deze editie beschikbaar in het Engels.
KEV is CISA’s catalogue of vulnerabilities known to be exploited. This explorer contains a complete dated snapshot, not a live feed. A CVE or product-name match is a lead to compare with the exact deployed product and version; it does not prove that a visitor’s system is vulnerable or compromised.
Entry names, products, descriptions, required actions and links retain CISA’s language and values. Explanations are editorial. Entries may be added or corrected after this snapshot; consult the official source before an operational decision.
- Vermeldingen
- 1769
- Verschillende leverancier-/projectnamen
- 291
- Publicatiedatum van de catalogus
Counters describe this snapshot only. They do not measure attack counts, vulnerability prevalence or an organisation’s risk. Distinct vendorProject labels are counted exactly as published, without merging aliases or treating them as distinct companies.
Unknown means CISA lacks confirmation of use in a ransomware campaign; it does not mean no exploitation. forensicTriage Yes/No is a separate field described by the schema with a reference to BOD 26-04. An absent field stays unreported. Neither No nor Unknown demonstrates that your asset has not been compromised.
dueDate is the deadline published in the CISA entry for the stated action. It is not a universal SLA, a patch release date or evidence that a patch was installed. The forensicTriage field alone cannot determine your obligations or define an investigation plan. The FedRAMP notice explains how its federal cloud certification programme aligns with BOD 26-04. Check which scope applies before adopting a deadline.
Six readings that prevent a misleading priority
| Published field | Useful reading | Conclusion to avoid |
|---|---|---|
| cveID | Join sources discussing the same vulnerability. | The identifier year does not date KEV inclusion. |
| vendorProject · product | Find the vendor advisory and local inventory. | A product name does not replace affected versions and configurations. |
| dateAdded | Date the entry’s inclusion in this catalogue. | Do not call it discovery or first-exploitation date. |
| dueDate · requiredAction | Read the published action and deadline together. | Do not turn the date into a universal obligation or proof of remediation. |
| knownRansomwareCampaignUse | Preserve Known, Unknown or an absent field. | Unknown is not No and does not remove the known exploitation signal underlying KEV. |
| forensicTriage · cwes | Separate CISA’s indicator from published weakness classes. | A CWE is not a specific product or score; No is not a certificate that no incident occurred. |
Toevoegingen aan de catalogus per jaar
| Jaar van toevoeging | Vermeldingen |
|---|---|
| 2021 | 311 |
| 2022 | 555 |
| 2023 | 187 |
| 2024 | 186 |
| 2025 | 245 |
| 2026 | 285 |
Resultaten : 555 / 1769 · Pagina 16 / 23
| CVE | Leverancier of project · product | Toevoegingsdatum / Termijn in de vermelding | Gebruik in ransomwarecampagnes / forensicTriage |
|---|---|---|---|
| CVE-2019-1405 | Microsoft Windows Door CISA gepubliceerde vermelding en maatregelMicrosoft Windows Universal Plug and Play (UPnP) Service Privilege Escalation VulnerabilityA privilege escalation vulnerability exists when the Windows UPnP service improperly allows COM object creation.
|
|
|
| CVE-2020-5135 CWE-120 | SonicWall SonicOS Door CISA gepubliceerde vermelding en maatregelSonicWall SonicOS Buffer Overflow VulnerabilityA buffer overflow vulnerability in SonicOS allows a remote attacker to cause Denial of Service (DoS) and potentially execute arbitrary code by sending a malicious request to the firewall.
|
|
|
| CVE-2009-3960 | Adobe BlazeDS Door CISA gepubliceerde vermelding en maatregelAdobe BlazeDS Information Disclosure VulnerabilityAdobe BlazeDS, which is utilized in LifeCycle and Coldfusion, contains a vulnerability that allows for information disclosure.
|
|
|
| CVE-2013-0625 CWE-255 | Adobe ColdFusion Door CISA gepubliceerde vermelding en maatregelAdobe ColdFusion Authentication Bypass VulnerabilityAdobe Coldfusion contains an authentication bypass vulnerability, which could result in an unauthorized user gaining administrative access.
|
|
|
| CVE-2013-0629 CWE-264 | Adobe ColdFusion Door CISA gepubliceerde vermelding en maatregelAdobe ColdFusion Directory Traversal VulnerabilityAdobe Coldfusion contains a directory traversal vulnerability, which could permit an unauthorized user access to restricted directories.
|
|
|
| CVE-2013-0631 CWE-200 | Adobe ColdFusion Door CISA gepubliceerde vermelding en maatregelAdobe ColdFusion Information Disclosure VulnerabilityAdobe Coldfusion contains an unspecified vulnerability, which could result in information disclosure from a compromised server.
|
|
|
| CVE-2016-6277 CWE-352 | NETGEAR Multiple Routers Door CISA gepubliceerde vermelding en maatregelNETGEAR Multiple Routers Remote Code Execution VulnerabilityNETGEAR confirmed multiple routers allow unauthenticated web pages to pass form input directly to the command-line interface, permitting remote code execution.
|
|
|
| CVE-2017-6077 CWE-78 | NETGEAR Wireless Router DGN2200 Door CISA gepubliceerde vermelding en maatregelNETGEAR DGN2200 Remote Code Execution VulnerabilityNETGEAR DGN2200 wireless routers contain a vulnerability that allows for remote code execution.
|
|
|
| CVE-2019-11581 CWE-74 | Atlassian Jira Server and Data Center Door CISA gepubliceerde vermelding en maatregelAtlassian Jira Server and Data Center Server-Side Template Injection VulnerabilityAtlassian Jira Server and Data Center contain a server-side template injection vulnerability which can allow for remote code execution.
|
|
|
| CVE-2020-8218 CWE-94 | Pulse Secure Pulse Connect Secure Door CISA gepubliceerde vermelding en maatregelPulse Connect Secure Code Injection VulnerabilityA code injection vulnerability exists in Pulse Connect Secure that allows an attacker to crafted a URI to perform an arbitrary code execution via the admin web interface.
|
|
|
| CVE-2021-21973 CWE-20, CWE-918 | VMware vCenter Server and Cloud Foundation Door CISA gepubliceerde vermelding en maatregelVMware vCenter Server and Cloud Foundation Server Side Request Forgery (SSRF) VulnerabilityVMware vCenter Server and Cloud Foundation Server contain a SSRF vulnerability due to improper validation of URLs in a vCenter Server plugin. This allows for information disclosure.
|
|
|
| CVE-2022-26485 CWE-416 | Mozilla Firefox Door CISA gepubliceerde vermelding en maatregelMozilla Firefox Use-After-Free VulnerabilityMozilla Firefox contains a use-after-free vulnerability in XSLT parameter processing which can be exploited to perform arbitrary code execution.
|
|
|
| CVE-2022-26486 CWE-416 | Mozilla Firefox Door CISA gepubliceerde vermelding en maatregelMozilla Firefox Use-After-Free VulnerabilityMozilla Firefox contains a use-after-free vulnerability in WebGPU IPC Framework which can be exploited to perform arbitrary code execution.
|
|
|
| CVE-2002-0367 | Microsoft Windows Door CISA gepubliceerde vermelding en maatregelMicrosoft Windows Privilege Escalation Vulnerabilitysmss.exe debugging subsystem in Microsoft Windows does not properly authenticate programs that connect to other programs, which allows local users to gain administrator or SYSTEM privileges.
|
|
|
| CVE-2004-0210 CWE-120 | Microsoft Windows Door CISA gepubliceerde vermelding en maatregelMicrosoft Windows Privilege Escalation VulnerabilityA privilege elevation vulnerability exists in the POSIX subsystem. This vulnerability could allow a logged on user to take complete control of the system.
|
|
|
| CVE-2008-2992 CWE-119 | Adobe Acrobat and Reader Door CISA gepubliceerde vermelding en maatregelAdobe Reader and Acrobat Input Validation VulnerabilityAdobe Acrobat and Reader contain an input validation issue in a JavaScript method that could potentially lead to remote code execution.
|
|
|
| CVE-2008-3431 CWE-264 | Oracle VirtualBox Door CISA gepubliceerde vermelding en maatregelOracle VirtualBox Insufficient Input Validation VulnerabilityAn input validation vulnerability exists in the VBoxDrv.sys driver of Sun xVM VirtualBox which allows attackers to locally execute arbitrary code.
|
|
|
| CVE-2009-1123 CWE-20 | Microsoft Windows Door CISA gepubliceerde vermelding en maatregelMicrosoft Windows Improper Input Validation VulnerabilityThe kernel in Microsoft Windows does not properly validate changes to unspecified kernel objects, which allows local users to gain privileges via a crafted application.
|
|
|
| CVE-2009-3129 CWE-94 | Microsoft Excel Door CISA gepubliceerde vermelding en maatregelMicrosoft Excel Featheader Record Memory Corruption VulnerabilityMicrosoft Office Excel allows remote attackers to execute arbitrary code via a spreadsheet with a FEATHEADER record containing an invalid cbHdrData size element that affects a pointer offset.
|
|
|
| CVE-2010-0188 CWE-94 | Adobe Reader and Acrobat Door CISA gepubliceerde vermelding en maatregelAdobe Reader and Acrobat Arbitrary Code Execution VulnerabilityUnspecified vulnerability in Adobe Reader and Acrobat allows attackers to cause a denial of service or possibly execute arbitrary code.
|
|
|
| CVE-2010-0232 CWE-264 | Microsoft Windows Door CISA gepubliceerde vermelding en maatregelMicrosoft Windows Kernel Exception Handler VulnerabilityThe kernel in Microsoft Windows, when access to 16-bit applications is enabled on a 32-bit x86 platform, does not properly validate certain BIOS calls, which allows local users to gain privileges.
|
|
|
| CVE-2010-3333 CWE-119 | Microsoft Office Door CISA gepubliceerde vermelding en maatregelMicrosoft Office Stack-based Buffer Overflow VulnerabilityA stack-based buffer overflow vulnerability exists in the parsing of RTF data in Microsoft Office and earlier allows an attacker to perform remote code execution.
|
|
|
| CVE-2011-0611 CWE-843 | Adobe Flash Player Door CISA gepubliceerde vermelding en maatregelAdobe Flash Player Remote Code Execution VulnerabilityAdobe Flash Player contains a vulnerability that allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via crafted Flash content.
|
|
|
| CVE-2011-1889 CWE-119 | Microsoft Forefront Threat Management Gateway (TMG) Door CISA gepubliceerde vermelding en maatregelMicrosoft Forefront TMG Remote Code Execution VulnerabilityA remote code execution vulnerability exists in the Forefront Threat Management Gateway (TMG) Firewall Client Winsock provider that could allow code execution in the security context of the client application.
|
|
|
| CVE-2011-3544 | Oracle Java SE JDK and JRE Door CISA gepubliceerde vermelding en maatregelOracle Java SE Runtime Environment (JRE) Arbitrary Code Execution VulnerabilityAn access control vulnerability exists in the Applet Rhino Script Engine component of Oracle's Java Runtime Environment allows an attacker to remotely execute arbitrary code.
|
|
|
An old identifier can enter the catalogue recently
CVE-2015-5477, associated with ISC BIND in this snapshot, has identifier year 2015 and dateAdded 8 October 2026. These dates answer different questions. The entry calls for following vendor instructions; it does not establish your BIND version, exposure or installation of a fix.
From a public signal to a documented decision
- Qualify the match
Keep the CVE, source and date, then establish product, version, embedded component and exposure. An SBOM may locate a component without proving its runtime condition.
- Read the action at its source
Open the vendor advisory and updates. Separate updating, mitigation, discontinuing a product and searching for compromise evidence; a patch does not replace these other decisions.
- Document the change
Assign an owner, prepare rollback and verify dependencies. A mitigation remains a scoped measure with an explicit validity period.
- Verify the resulting state
Retain an observed version, checked configuration and service test. Closing a task needs evidence concerning the actual asset, beyond a console status.
Source release : · Documentary review :
- CISA · KEV official snapshot · 2026.11.06
- CISA · Current KEV JSON in the official repository · Live repository file
- CISA · KEV data schema · JSON Schema Draft 07 · pinned source
- CISA · Official mirror and reuse terms · Official repository · pinned source
- CISA · KEV licence · CC0 1.0 Universal
- FedRAMP · Response to CISA BOD 26-04 · Notice NTC-0014 · 16 June 2026
- FIRST · CVSS · CVSS 4.0
- FIRST · EPSS · Living documentation · reviewed 2026-10-22
CISA KEV data reused under CC0 1.0. Reuse implies no CISA affiliation or endorsement and grants no right to use the CISA logo or DHS seal.
Broninformatie · CISA KEV
How we publish this official snapshot
De uitgebreide toelichtingen zijn in deze editie beschikbaar in het Engels.
The copy is identified by its catalogue version, dateReleased, official mirror commit and source-file digest. CISA publication, GitHub synchronisation and our review are distinct events. Aggregates are computed from the retained entries; no visitor inventory collection or vulnerability scan takes place.
- catalogVersion
2026.11.06- dateReleased
- GitHub commit
e5b3a9b25050a8da26c96266c5bfe438ee0bdebc·- SHA-256
47e0406b2be5a40420eff66f3d90e83eb8883dae6ff4d08e1b2a942c366f6cc2
Counters describe this snapshot only. They do not measure attack counts, vulnerability prevalence or an organisation’s risk. Distinct vendorProject labels are counted exactly as published, without merging aliases or treating them as distinct companies.
Catalogus en methode bekijken →
Source release : · Documentary review :
- CISA · KEV official snapshot · 2026.11.06
- CISA · Current KEV JSON in the official repository · Live repository file
- CISA · KEV data schema · JSON Schema Draft 07 · pinned source
- CISA · Official mirror and reuse terms · Official repository · pinned source
- CISA · KEV licence · CC0 1.0 Universal
- FedRAMP · Response to CISA BOD 26-04 · Notice NTC-0014 · 16 June 2026
- FIRST · CVSS · CVSS 4.0
- FIRST · EPSS · Living documentation · reviewed 2026-10-22
CISA KEV data reused under CC0 1.0. Reuse implies no CISA affiliation or endorsement and grants no right to use the CISA logo or DHS seal.
Officiële referenties
Referenties ondersteunen de methode. Pas controles aan uw context aan; ze zijn geen certificering. Originele referentietitels en brondocumenten kunnen in een andere taal zijn.
Bronnen geraadpleegd op .
- NIST SP 800-40 Rev. 4 — enterprise patch management
- CISA — Known Exploited Vulnerabilities Catalog
- FIRST · CVSS
- FIRST · EPSS
- CISA · Known Exploited Vulnerabilities
- SLSA 1.2 · Build: Verifying artifacts
- SLSA 1.2 · Build: Provenance
- SLSA 1.2 · Build: Track Basics
- in-toto · Statement v1
- Sigstore · Verifying Signatures
- CISA · KEV official snapshot
- CISA · Current KEV JSON in the official repository
- CISA · KEV data schema
- CISA · Official mirror and reuse terms
- CISA · KEV licence
- FedRAMP · Response to CISA BOD 26-04
- FIRST · CVSS
- FIRST · EPSS Frequently Asked Questions
- CISA · KEV official data schema
- OpenVEX · Specification v0.2.0
