Risorse · 23
Dare priorità alle vulnerabilità e verificare la correzione
Collegare lo sfruttamento noto, le risorse esposte, l'impatto aziendale e la prova di una correzione funzionante.
Aggiornato · 9 min
Obiettivi di questa guida
- Associare gli avvisi alle risorse
- Classificare l'urgenza effettiva
- Implementare in sicurezza
- Verificare e chiudere
Verifica rapida
- Il prodotto e la versione interessati sono effettivamente distribuiti?
- La risorsa è raggiungibile ed è critica per l'attività aziendale?
- Lo sfruttamento è documentato?
- Cosa protegge il servizio prima di una patch?
- Un controllo conferma che il problema è stato risolto sulla risorsa?
Metodo passo passo
- 1
Consolidare l'inventario
Mappare servizi, prodotti, versioni, ambienti, esposizione e responsabili. Un avviso di componente da solo non dimostra che un'istanza vulnerabile sia distribuita.
Risultato: elenco datato delle risorse interessate e delle incertezze.
- 2
Qualificare il risultato
Confrontare l'avviso del fornitore, l'identificativo CVE, le condizioni di sfruttamento e, ove pertinente, il catalogo CISA delle vulnerabilità note sfruttate. Registrare quando è stata verificata ciascuna fonte.
Risultato: risultato con riferimenti primari.
- 3
Definire una priorità difendibile
Considerare lo sfruttamento noto, l'accessibilità delle risorse, i privilegi richiesti, i dati gestiti, l'impatto sul servizio e le soluzioni disponibili. Assegnare un responsabile e una scadenza specifica per il contesto.
Risultato: decisione motivata sulla priorità.
- 4
Preparare la modifica
Mappare le dipendenze, la finestra temporale per la modifica, il backup e il rollback. Se un aggiornamento non può essere applicato tempestivamente, registrare il controllo temporaneo e la sua scadenza.
Risultato: piano di implementazione ed eccezione limitata.
- 5
Implementare e testare
Applicare la correzione o la mitigazione del fornitore utilizzando il processo approvato. Verificare la versione risultante, il flusso di lavoro aziendale e le integrazioni che potrebbero presentare regressioni.
Risultato atteso: registro di implementazione e risultato funzionale.
- 6
Verifica della chiusura
Verifica dell'asset effettivo con un metodo appropriato, individua le istanze mancanti e rivedi le eccezioni. Non chiudere un ticket solo perché è stato programmato un aggiornamento.
Risultato atteso: documentazione di verifica e registro aggiornato.
Indicatori di gestione
| Indicatore | Cosa misura | Prima azione |
|---|---|---|
| Copertura | Risorse critiche con versioni e proprietari noti | Completare l'inventario |
| Ritardo | Tempo dalla qualificazione alla correzione verificata | Rimuovere i colli di bottiglia ripetuti |
| Verifica | Correzioni ritestate su risorse reali | Riaprire le chiusure senza prove |
| Eccezioni | Deroghe con controllo, proprietario e scadenza | Chiudere le eccezioni scadute |
Errori comuni
- Classificazione basata esclusivamente su un punteggio generico senza verificare la risorsa
- Presumere che un'inclusione in un elenco KEV implichi l'esistenza del prodotto nel proprio parco
- Implementazione senza testare il comportamento del servizio
- Lasciare i controlli compensativi senza una data di revisione
Domande frequenti
La CVE con il punteggio più alto deve sempre essere eseguita per prima?
Un punteggio descrive la gravità tecnica; lo sfruttamento noto, l'esposizione e l'impatto sul servizio locale guidano l'ordine operativo.
Cosa fare se non esiste una patch?
Seguire le misure di mitigazione del fornitore, ridurre l'esposizione ove possibile e documentare il responsabile, la data di revisione e il rischio residuo.
Quando il lavoro è chiuso?
Dopo che la versione o la misura di mitigazione è stata verificata sulle istanze interessate e la funzionalità critica è stata testata.
Riferimenti: dati, usi e limiti
Documentazione consultata il .
Le note dettagliate di questa edizione sono disponibili in inglese.
| Fonte e finalità | Dato o riferimento verificato | Come utilizzarlo | Limite da conservare |
|---|---|---|---|
| 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 e VEX
Le note dettagliate di questa edizione sono disponibili in inglese.
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
Firma e provenienza del build
Le note dettagliate di questa edizione sono disponibili in inglese.
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
Esplora il catalogo KEV di CISA
Le note dettagliate di questa edizione sono disponibili in inglese.
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.
- Voci
- 1769
- Etichette distinte di fornitore/progetto
- 291
- Pubblicazione del catalogo
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. |
Inserimenti nel catalogo per anno
| Anno di inserimento | Voci |
|---|---|
| 2021 | 311 |
| 2022 | 555 |
| 2023 | 187 |
| 2024 | 186 |
| 2025 | 245 |
| 2026 | 285 |
Risultati : 1769 / 1769 · Pagina 65 / 71
| CVE | Fornitore o progetto · product | Data di inserimento / Scadenza della voce | Uso in campagne ransomware / forensicTriage |
|---|---|---|---|
| CVE-2020-14871 CWE-787 | Oracle Solaris and Zettabyte File System (ZFS) Voce e azione pubblicate da CISAOracle Solaris and Zettabyte File System (ZFS) Unspecified VulnerabilityOracle Solaris and Oracle ZFS Storage Appliance Kit contain an unspecified vulnerability causing high impacts to confidentiality, integrity, and availability of affected systems.
|
|
|
| CVE-2020-14882 | Oracle WebLogic Server Voce e azione pubblicate da CISAOracle WebLogic Server Remote Code Execution VulnerabilityOracle WebLogic Server contains an unspecified vulnerability, which is assessed to allow for remote code execution, based on this vulnerability being related to CVE-2020-14750.
|
|
|
| CVE-2020-14883 | Oracle WebLogic Server Voce e azione pubblicate da CISAOracle WebLogic Server Unspecified VulnerabilityOracle WebLogic Server contains an unspecified vulnerability in the Console component with high impacts to confidentilaity, integrity, and availability.
|
|
|
| CVE-2020-15505 CWE-706 | Ivanti MobileIron Multiple Products Voce e azione pubblicate da CISAIvanti MobileIron Multiple Products Remote Code Execution VulnerabilityIvanti MobileIron's Core & Connector, Sentry, and Monitor and Reporting Database (RDB) products contain an unspecified vulnerability that allows for remote code execution.
|
|
|
| CVE-2020-15999 CWE-787 | Google Chrome FreeType Voce e azione pubblicate da CISAGoogle Chrome FreeType Heap Buffer Overflow VulnerabilityGoogle Chrome uses FreeType, an open-source software library to render fonts, which contains a heap buffer overflow vulnerability in the function Load_SBit_Png when processing PNG images embedded into fonts. This vulnerability is part of an exploit chain with CVE-2020-17087 on Windows and CVE-2020-16010 on Android.
|
|
|
| CVE-2020-16009 CWE-787, CWE-843 | Google Chromium V8 Voce e azione pubblicate da CISAGoogle Chromium V8 Type Confusion VulnerabilityGoogle Chromium V8 Engine contains a type confusion vulnerability that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.
|
|
|
| CVE-2020-16010 CWE-787 | Google Chrome for Android UI Voce e azione pubblicate da CISAGoogle Chrome for Android UI Heap Buffer Overflow VulnerabilityGoogle Chrome for Android UI contains a heap buffer overflow vulnerability that allows a remote attacker, who has compromised the renderer process, to potentially perform a sandbox escape via a crafted HTML page.
|
|
|
| CVE-2020-16013 CWE-787 | Google Chromium V8 Voce e azione pubblicate da CISAGoogle Chromium V8 Incorrect Implementation VulnerabililtyGoogle Chromium V8 Engine contains an inappropriate implementation vulnerability that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.
|
|
|
| CVE-2020-16017 CWE-416 | Google Chrome Voce e azione pubblicate da CISAGoogle Chrome Use-After-Free VulnerabilityGoogle Chrome contains a use-after-free vulnerability that allows a remote attacker, who has compromised the renderer process, to potentially perform a sandbox escape via a crafted HTML page.
|
|
|
| CVE-2020-16846 CWE-78 | SaltStack Salt Voce e azione pubblicate da CISASaltStack Salt Shell Injection VulnerabilitySaltStack Salt allows an unauthenticated user with network access to the Salt API to use shell injections to run code on the Salt API using the SSH client. This vulnerability affects any users running the Salt API.
|
|
|
| CVE-2020-17087 CWE-131 | Microsoft Windows Voce e azione pubblicate da CISAMicrosoft Windows Kernel Privilege Escalation VulnerabilityMicrosoft Windows kernel contains an unspecified vulnerability that allows for privilege escalation.
|
|
|
| CVE-2020-17144 CWE-502 | Microsoft Exchange Server Voce e azione pubblicate da CISAMicrosoft Exchange Server Remote Code Execution VulnerabilityMicrosoft Exchange Server improperly validates cmdlet arguments which allow an attacker to perform remote code execution.
|
|
|
| CVE-2020-17496 CWE-74 | vBulletin vBulletin Voce e azione pubblicate da CISAvBulletin PHP Module Remote Code Execution VulnerabilityThe PHP module within vBulletin contains an unspecified vulnerability that allows for remote code execution via crafted subWidgets data in an ajax/render/widget_tabbedcontainer_tab_panel request. This CVE ID resolves an incomplete patch for CVE-2019-16759.
|
|
|
| CVE-2020-17530 CWE-917 | Apache Struts Voce e azione pubblicate da CISAApache Struts Remote Code Execution VulnerabilityForced Object-Graph Navigation Language (OGNL) evaluation in Apache Struts, when evaluated on raw user input in tag attributes, can lead to remote code execution.
|
|
|
| CVE-2020-24557 | Trend Micro Apex One, OfficeScan, and Worry-Free Business Security Voce e azione pubblicate da CISATrend Micro Multiple Products Improper Access Control VulnerabilityTrend Micro Apex One, OfficeScan, and Worry-Free Business Security on Microsoft Windows contain an improper access control vulnerability that may allow an attacker to manipulate a particular product folder to disable the security temporarily, abuse a specific Windows function, and attain privilege escalation.
|
|
|
| CVE-2020-25213 CWE-434 | WordPress File Manager Plugin Voce e azione pubblicate da CISAWordPress File Manager Plugin Remote Code Execution VulnerabilityWordPress File Manager plugin contains a remote code execution vulnerability that allows unauthenticated users to execute PHP code and upload malicious files on a target site.
|
|
|
| CVE-2020-25506 CWE-78 | D-Link DNS-320 Device Voce e azione pubblicate da CISAD-Link DNS-320 Device Command Injection VulnerabilityD-Link DNS-320 device contains a command injection vulnerability in the sytem_mgr.cgi component that may allow for remote code execution.
|
|
|
| CVE-2020-2555 CWE-502 | Oracle Multiple Products Voce e azione pubblicate da CISAOracle Multiple Products Remote Code Execution VulnerabilityMultiple Oracle products contain a remote code execution vulnerability that allows an unauthenticated attacker with network access via T3 or HTTP to takeover the affected system. Impacted Oracle products: Oracle Coherence in Fusion Middleware, Oracle Utilities Framework, Oracle Retail Assortment Planning, Oracle Commerce, Oracle Communications Diameter Signaling Router (DSR).
|
|
|
| CVE-2020-26919 | NETGEAR JGS516PE Devices Voce e azione pubblicate da CISANetgear JGS516PE Devices Missing Function Level Access Control VulnerabilityNetgear JGS516PE devices contain a missing function level access control vulnerability.
|
|
|
| CVE-2020-27930 CWE-787 | Apple Multiple Products Voce e azione pubblicate da CISAApple Multiple Products Memory Corruption VulnerabilityApple iOS, iPadOS, macOS, and watchOS FontParser contain a memory corruption vulnerability which may allow for code execution when processing maliciously crafted front.
|
|
|
| CVE-2020-27932 CWE-843 | Apple Multiple Products Voce e azione pubblicate da CISAApple Multiple Products Type Confusion VulnerabilityApple iOS, iPadOS, macOS, and watchOS contain a type confusion vulnerability that may allow a malicious application to execute code with kernel privileges.
|
|
|
| CVE-2020-27950 CWE-665 | Apple Multiple Products Voce e azione pubblicate da CISAApple Multiple Products Memory Initialization VulnerabilityApple iOS, iPadOS, macOS, and watchOS contain a memory initialization vulnerability that may allow a malicious application to disclose kernel memory.
|
|
|
| CVE-2020-29557 CWE-119 | D-Link DIR-825 R1 Devices Voce e azione pubblicate da CISAD-Link DIR-825 R1 Devices Buffer Overflow VulnerabilityD-Link DIR-825 R1 devices contain a buffer overflow vulnerability in the web interface that may allow for remote code execution.
|
|
|
| CVE-2020-29583 CWE-522 | Zyxel Multiple Products Voce e azione pubblicate da CISAZyxel Multiple Products Use of Hard-Coded Credentials VulnerabilityZyxel firewalls (ATP, USG, VM) and AP Controllers (NXC2500 and NXC5500) contain a use of hard-coded credentials vulnerability in an undocumented account ("zyfwp") with an unchangeable password.
|
|
|
| CVE-2020-3118 CWE-134 | Cisco IOS XR Voce e azione pubblicate da CISACisco IOS XR Software Discovery Protocol Format String VulnerabilityCisco IOS XR improperly validates string input from certain fields in Cisco Discovery Protocol messages. Exploitation could allow an unauthenticated, adjacent attacker to execute code with administrative privileges or cause a reload on an affected device.
|
|
|
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.
Informazioni documentali · CISA KEV
How we publish this official snapshot
Le note dettagliate di questa edizione sono disponibili in inglese.
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.
Esplora il catalogo e il metodo →
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.
Riferimenti ufficiali
I riferimenti supportano il metodo. Adattare i controlli al proprio contesto; non costituiscono una certificazione. I titoli dei riferimenti originali e i documenti di origine potrebbero essere in un'altra lingua.
Riferimenti consultati il .
- 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
