Recursos · 23
Priorizar vulnerabilidades y verificar su remediación
Conecte la explotación conocida, los activos expuestos, el impacto comercial y la prueba de una solución que funciona.
Actualizado · 9 min
Lo que esta guía ayuda a lograr
- Coincidencia de alertas con activos
- Ranking urgencia real
- Despliegue de forma segura
- Verificar y cerrar
Comprobación rápida
- ¿Está realmente implementado el producto y la versión afectados?
- ¿El activo es accesible y crítico para el negocio?
- ¿Está documentada la explotación?
- ¿Qué protege el servicio ante un parche?
- ¿Una verificación confirma que el problema desapareció del activo?
Método paso a paso
- 1
Consolidar el inventario
Servicios de mapas, productos, versiones, entornos, exposición y propietarios. Un aviso de componente por sí solo no prueba que se haya implementado una instancia vulnerable.
Entregable: lista fechada de activos afectados e incertidumbres.
- 2
Calificar el hallazgo
Compare el aviso del proveedor, el identificador CVE, las condiciones de explotación y, cuando sea relevante, el catálogo de CISA de vulnerabilidades explotadas conocidas. Registre cuándo se verificó cada fuente.
Entregable: hallazgo con referencias primarias.
- 3
Establecer una prioridad defendible
Considere la explotación conocida, la accesibilidad de los activos, los privilegios requeridos, los datos manejados, el impacto del servicio y la reparación disponible. Asigne un propietario y una fecha límite específica del contexto.
Entregable: decisión de prioridad razonada.
- 4
Preparar el cambio
Mapear dependencias, cambiar ventana, backup y rollback. Si una actualización no se puede aplicar rápidamente, registre el control temporal y su vencimiento.
Entregable: plan de implementación y excepción limitada.
- 5
Implementar y probar
Aplicar la solución o mitigación del proveedor mediante el proceso aprobado. Verifique la versión resultante, el recorrido comercial y las integraciones que pueden retroceder.
Entregable: registro de despliegue y resultado funcional.
- 6
Verificar cierre
Verifique el activo real con un método adecuado, encuentre instancias perdidas y revise las excepciones. No cierre un ticket porque simplemente se programó una actualización.
Entregable: evidencias de verificación y registro actualizado.
Indicadores de gestión
| Indicador | Qué mide | Primera acción |
|---|---|---|
| Cobertura | Activos críticos con versiones y propietarios conocidos | Completar el inventario |
| Retraso | Tiempo desde la calificación hasta la corrección verificada | Eliminar cuellos de botella repetidos |
| Verificación | Correcciones probadas nuevamente en activos reales | Reabrir cierres sin pruebas |
| Excepciones | Renuncias con control, titular y caducidad | Cerrar excepciones caducadas |
Errores comunes
- Ranking únicamente por puntuación genérica sin comprobar el activo
- Asumir un listado KEV significa que el producto existe en su patrimonio
- Implementar sin probar el comportamiento del servicio
- Salir de los controles compensatorios sin fecha de revisión
Preguntas frecuentes
¿El CVE con mayor puntuación siempre debe ir primero?
Una puntuación describe la severidad técnica; La explotación conocida, la exposición y el impacto del servicio local guían su orden operativo.
¿Qué pasa si no existe ningún parche?
Siga las mitigaciones de los proveedores, reduzca la exposición cuando sea posible y documente el propietario, la fecha de revisión y el riesgo residual.
¿Cuándo cierra la obra?
Después de que se haya verificado la versión o mitigación en las instancias afectadas y se haya probado la funcionalidad crítica.
Referencias: datos, usos y límites
Documentación consultada el .
Las notas detalladas de esta edición están disponibles en inglés.
| Fuente y finalidad | Dato o referencia verificada | Cómo utilizarla | Límite que debe conservarse |
|---|---|---|---|
| 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 y VEX
Las notas detalladas de esta edición están disponibles en inglés.
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 y procedencia del build
Las notas detalladas de esta edición están disponibles en inglés.
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
Explorar el catálogo KEV de CISA
Las notas detalladas de esta edición están disponibles en inglés.
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.
- Registros
- 1769
- Etiquetas distintas de proveedor/proyecto
- 291
- Publicación del catálogo
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. |
Incorporaciones al catálogo por año
| Año de incorporación | Registros |
|---|---|
| 2021 | 311 |
| 2022 | 555 |
| 2023 | 187 |
| 2024 | 186 |
| 2025 | 245 |
| 2026 | 285 |
Resultados : 555 / 1769 · Página 3 / 23
| CVE | Proveedor o proyecto · product | Fecha de incorporación / Fecha límite del registro | Uso en campañas de ransomware / forensicTriage |
|---|---|---|---|
| CVE-2018-7445 CWE-119 | MikroTik RouterOS Registro y acción publicados por CISAMikroTik RouterOS Stack-Based Buffer Overflow VulnerabilityIn MikroTik RouterOS, a stack-based buffer overflow occurs when processing NetBIOS session request messages. Remote attackers with access to the service can exploit this vulnerability and gain code execution on the system.
|
|
|
| CVE-2020-9934 | Apple iOS, iPadOS, and macOS Registro y acción publicados por CISAApple iOS, iPadOS, and macOS Input Validation VulnerabilityApple iOS, iPadOS, and macOS contain an unspecified vulnerability involving input validation which can allow a local attacker to view sensitive user information.
|
|
|
| CVE-2022-26258 CWE-78 | D-Link DIR-820L Registro y acción publicados por CISAD-Link DIR-820L Remote Code Execution VulnerabilityD-Link DIR-820L contains an unspecified vulnerability in Device Name parameter in /lan.asp which allows for remote code execution.
|
|
|
| CVE-2022-27593 CWE-610 | QNAP Photo Station Registro y acción publicados por CISAQNAP Photo Station Externally Controlled Reference VulnerabilityCertain QNAP NAS running Photo Station with internet exposure contain an externally controlled reference to a resource vulnerability which can allow an attacker to modify system files. This vulnerability was observed being utilized in a Deadbolt ransomware campaign.
|
|
|
| CVE-2022-3075 CWE-20 | Google Chromium Mojo Registro y acción publicados por CISAGoogle Chromium Mojo Insufficient Data Validation VulnerabilityGoogle Chromium Mojo contains an insufficient data validation vulnerability that allows a remote attacker, who has compromised the renderer process, to potentially perform a sandbox escape 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-28949 CWE-74 | PEAR Archive_Tar Registro y acción publicados por CISAPEAR Archive_Tar Deserialization of Untrusted Data VulnerabilityPEAR Archive_Tar allows an unserialization attack because phar: is blocked but PHAR: is not blocked. PEAR stands for PHP Extension and Application Repository and it is an open-source framework and distribution system for reusable PHP components with known usage in third-party products such as Drupal Core and Red Hat Linux.
|
|
|
| CVE-2020-36193 CWE-22, CWE-59 | PEAR Archive_Tar Registro y acción publicados por CISAPEAR Archive_Tar Improper Link Resolution VulnerabilityPEAR Archive_Tar Tar.php allows write operations with directory traversal due to inadequate checking of symbolic links. PEAR stands for PHP Extension and Application Repository and it is an open-source framework and distribution system for reusable PHP components with known usage in third-party products such as Drupal Core and Red Hat Linux.
|
|
|
| CVE-2021-31010 CWE-20, CWE-502 | Apple iOS, macOS, watchOS Registro y acción publicados por CISAApple iOS, macOS, watchOS Sandbox Bypass VulnerabilityIn affected versions of Apple iOS, macOS, and watchOS, a sandboxed process may be able to circumvent sandbox restrictions.
|
|
|
| CVE-2021-38406 CWE-787 | Delta Electronics DOPSoft 2 Registro y acción publicados por CISADelta Electronics DOPSoft 2 Improper Input Validation VulnerabilityDelta Electronics DOPSoft 2 lacks proper validation of user-supplied data when parsing specific project files (improper input validation) resulting in an out-of-bounds write that allows for code execution.
|
|
|
| CVE-2021-39226 CWE-287 | Grafana Labs Grafana Registro y acción publicados por CISAGrafana Authentication Bypass VulnerabilityGrafana contains an authentication bypass vulnerability that allows authenticated and unauthenticated users to view and delete all snapshot data, potentially resulting in complete snapshot data loss.
|
|
|
| CVE-2022-2294 CWE-122 | WebRTC WebRTC Registro y acción publicados por CISAWebRTC Heap Buffer Overflow VulnerabilityWebRTC, an open-source project providing web browsers with real-time communication, contains a heap buffer overflow vulnerability that allows an attacker to perform shellcode execution. This vulnerability impacts web browsers using WebRTC including but not limited to Google Chrome.
|
|
|
| CVE-2022-22963 CWE-94 | VMware Tanzu Spring Cloud Registro y acción publicados por CISAVMware Tanzu Spring Cloud Function Remote Code Execution VulnerabilityWhen using routing functionality in VMware Tanzu's Spring Cloud Function, it is possible for a user to provide a specially crafted SpEL as a routing-expression that may result in remote code execution and access to local resources.
|
|
|
| CVE-2022-24112 CWE-290 | Apache APISIX Registro y acción publicados por CISAApache APISIX Authentication Bypass VulnerabilityApache APISIX contains an authentication bypass vulnerability that allows for remote code execution.
|
|
|
| CVE-2022-24706 CWE-1188 | Apache CouchDB Registro y acción publicados por CISAApache CouchDB Insecure Default Initialization of Resource VulnerabilityApache CouchDB contains an insecure default initialization of resource vulnerability which can allow an attacker to escalate to administrative privileges.
|
|
|
| CVE-2022-26352 CWE-22, CWE-138 | dotCMS dotCMS Registro y acción publicados por CISAdotCMS Unrestricted Upload of File VulnerabilitydotCMS ContentResource API contains an unrestricted upload of file with a dangerous type vulnerability that allows for directory traversal, in which the file is saved outside of the intended storage location. Exploitation allows for remote code execution.
|
|
|
| CVE-2022-0028 CWE-940 | Palo Alto Networks PAN-OS Registro y acción publicados por CISAPalo Alto Networks PAN-OS Reflected Amplification Denial-of-Service VulnerabilityA Palo Alto Networks PAN-OS URL filtering policy misconfiguration could allow a network-based attacker to conduct reflected and amplified TCP denial-of-service (RDoS) attacks.
|
|
|
| CVE-2017-15944 | Palo Alto Networks PAN-OS Registro y acción publicados por CISAPalo Alto Networks PAN-OS Remote Code Execution VulnerabilityPalo Alto Networks PAN-OS contains multiple, unspecified vulnerabilities which can allow for remote code execution when chained.
|
|
|
| CVE-2022-21971 CWE-824 | Microsoft Windows Registro y acción publicados por CISAMicrosoft Windows Runtime Remote Code Execution VulnerabilityMicrosoft Windows Runtime contains an unspecified vulnerability that allows for remote code execution.
|
|
|
| CVE-2022-22536 CWE-444 | SAP Multiple Products Registro y acción publicados por CISASAP Multiple Products HTTP Request Smuggling VulnerabilitySAP NetWeaver Application Server ABAP, SAP NetWeaver Application Server Java, ABAP Platform, SAP Content Server and SAP Web Dispatcher allow HTTP request smuggling. An unauthenticated attacker can prepend a victim's request with arbitrary data, allowing for function execution impersonating the victim or poisoning intermediary Web caches.
|
|
|
| CVE-2022-26923 CWE-295 | Microsoft Active Directory Registro y acción publicados por CISAMicrosoft Active Directory Domain Services Privilege Escalation VulnerabilityAn authenticated user could manipulate attributes on computer accounts they own or manage, and acquire a certificate from Active Directory Certificate Services that would allow for privilege escalation to SYSTEM.
|
|
|
| CVE-2022-2856 CWE-20 | Google Chromium Intents Registro y acción publicados por CISAGoogle Chromium Intents Insufficient Input Validation VulnerabilityGoogle Chromium Intents contains an insufficient validation of untrusted input vulnerability that allows a remote attacker to browse to a malicious website 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-2022-32893 CWE-20, CWE-787 | Apple iOS and macOS Registro y acción publicados por CISAApple iOS and macOS Out-of-Bounds Write VulnerabilityApple iOS and macOS contain an out-of-bounds write vulnerability that could allow for remote code execution when processing malicious crafted web content.
|
|
|
| CVE-2022-32894 CWE-20, CWE-787 | Apple iOS and macOS Registro y acción publicados por CISAApple iOS and macOS Out-of-Bounds Write VulnerabilityApple iOS and macOS contain an out-of-bounds write vulnerability that could allow an application to execute code with kernel privileges.
|
|
|
| CVE-2022-27925 CWE-22 | Synacor Zimbra Collaboration Suite (ZCS) Registro y acción publicados por CISASynacor Zimbra Collaboration Suite (ZCS) Arbitrary File Upload VulnerabilitySynacor Zimbra Collaboration Suite (ZCS) contains flaw in the mboximport functionality, allowing an authenticated attacker to upload arbitrary files to perform remote code execution. This vulnerability was chained with CVE-2022-37042 which allows for unauthenticated remote code execution.
|
|
|
| CVE-2022-37042 CWE-23 | Synacor Zimbra Collaboration Suite (ZCS) Registro y acción publicados por CISASynacor Zimbra Collaboration Suite (ZCS) Authentication Bypass VulnerabilitySynacor Zimbra Collaboration Suite (ZCS) contains an authentication bypass vulnerability in MailboxImportServlet. This vulnerability was chained with CVE-2022-27925 which allows for unauthenticated remote code execution.
|
|
|
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.
Información documental · CISA KEV
How we publish this official snapshot
Las notas detalladas de esta edición están disponibles en inglés.
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.
Explorar el catálogo y el método →
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.
Referencias oficiales
Las referencias respaldan el método. Adapte los controles a su contexto; no constituyen certificación. Los títulos de referencia originales y los documentos fuente pueden estar en otro idioma.
Referencias consultadas el .
- 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
