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 : 1769 / 1769 · Página 15 / 71
| CVE | Proveedor o proyecto · product | Fecha de incorporación / Fecha límite del registro | Uso en campañas de ransomware / forensicTriage |
|---|---|---|---|
| CVE-2025-32463 CWE-829 | Sudo Sudo Registro y acción publicados por CISASudo Inclusion of Functionality from Untrusted Control Sphere VulnerabilitySudo contains an inclusion of functionality from untrusted control sphere vulnerability. This vulnerability could allow local attacker to leverage sudo’s -R (--chroot) option to run arbitrary commands as root, even if they are not listed in the sudoers file.
|
|
|
| CVE-2025-59689 CWE-77 | Libraesva Email Security Gateway Registro y acción publicados por CISALibraesva Email Security Gateway Command Injection VulnerabilityLibraesva Email Security Gateway (ESG) contains a command injection vulnerability which allows command injection via a compressed e-mail attachment.
|
|
|
| CVE-2025-20333 CWE-120 | Cisco Secure Firewall Adaptive Security Appliance and Secure Firewall Threat Defense Registro y acción publicados por CISACisco Secure Firewall Adaptive Security Appliance (ASA) and Secure Firewall Threat Defense (FTD) Buffer Overflow VulnerabilityCisco Secure Firewall Adaptive Security (ASA) Appliance and Secure Firewall Threat Defense (FTD) Software VPN Web Server contain a buffer overflow vulnerability that allows for remote code execution. This vulnerability could be chained with CVE-2025-20362.
|
|
|
| CVE-2025-20362 CWE-862 | Cisco Secure Firewall Adaptive Security Appliance and Secure Firewall Threat Defense Registro y acción publicados por CISACisco Secure Firewall Adaptive Security (ASA) Appliance and Secure Firewall Threat Defense (FTD) Missing Authorization VulnerabilityCisco Secure Firewall Adaptive Security (ASA) Appliance and Secure Firewall Threat Defense (FTD) Software VPN Web Server contain a missing authorization vulnerability. This vulnerability could be chained with CVE-2025-20333.
|
|
|
| CVE-2025-10585 CWE-843 | Google Chromium V8 Registro y acción publicados por CISAGoogle Chromium V8 Type Confusion VulnerabilityGoogle Chromium contains a type confusion vulnerability in the V8 JavaScript and WebAssembly engine.
|
|
|
| CVE-2025-5086 CWE-502 | Dassault Systèmes DELMIA Apriso Registro y acción publicados por CISADassault Systèmes DELMIA Apriso Deserialization of Untrusted Data VulnerabilityDassault Systèmes DELMIA Apriso contains a deserialization of untrusted data vulnerability that could lead to a remote code execution.
|
|
|
| CVE-2025-38352 CWE-367 | Linux Kernel Registro y acción publicados por CISALinux Kernel Time-of-Check Time-of-Use (TOCTOU) Race Condition VulnerabilityLinux kernel contains a time-of-check time-of-use (TOCTOU) race condition vulnerability that has a high impact on confidentiality, integrity, and availability.
|
|
|
| CVE-2025-48543 | Android Runtime Registro y acción publicados por CISAAndroid Runtime Use-After-Free VulnerabilityAndroid Runtime contains a use-after-free vulnerability potentially allowing a chrome sandbox escape leading to local privilege escalation.
|
|
|
| CVE-2025-53690 CWE-502 | Sitecore Multiple Products Registro y acción publicados por CISASitecore Multiple Products Deserialization of Untrusted Data VulnerabilitySitecore Experience Manager (XM), Experience Platform (XP), Experience Commerce (XC), and Managed Cloud contain a deserialization of untrusted data vulnerability involving the use of default machine keys. This flaw allows attackers to exploit exposed ASP.NET machine keys to achieve remote code execution.
|
|
|
| CVE-2023-50224 CWE-290 | TP-Link TL-WR841N Registro y acción publicados por CISATP-Link TL-WR841N Authentication Bypass by Spoofing VulnerabilityTP-Link TL-WR841N contains an authentication bypass by spoofing vulnerability within the httpd service, which listens on TCP port 80 by default, leading to the disclose of stored credentials. The impacted products could be end-of-life (EoL) and/or end-of-service (EoS). Users should discontinue product utilization.
|
|
|
| CVE-2025-9377 CWE-78 | TP-Link Multiple Routers Registro y acción publicados por CISATP-Link Archer C7(EU) and TL-WR841N/ND(MS) OS Command Injection VulnerabilityTP-Link Archer C7(EU) and TL-WR841N/ND(MS) contain an OS command injection vulnerability that exists in the Parental Control page. The impacted products could be end-of-life (EoL) and/or end-of-service (EoS). Users should discontinue product utilization.
|
|
|
| CVE-2020-24363 CWE-306 | TP-Link TL-WA855RE Registro y acción publicados por CISATP-link TL-WA855RE Missing Authentication for Critical Function VulnerabilityTP-link TL-WA855RE contains a missing authentication for critical function vulnerability. This vulnerability could allow an unauthenticated attacker (on the same network) to submit a TDDP_RESET POST request for a factory reset and reboot. The attacker can then obtain incorrect access control by setting a new administrative password. The impacted products could be end-of-life (EoL) and/or end-of-service (EoS). Users should discontinue product utilization.
|
|
|
| CVE-2025-55177 CWE-863 | Meta PlatformsRegistro y acción publicados por CISAMeta Platforms WhatsApp Incorrect Authorization VulnerabilityMeta Platforms WhatsApp contains an incorrect authorization vulnerability due to an incomplete authorization of linked device synchronization messages. This vulnerability could allow an unrelated user to trigger processing of content from an arbitrary URL on a target’s device.
|
|
|
| CVE-2025-57819 CWE-89, CWE-288 | Sangoma FreePBX Registro y acción publicados por CISASangoma FreePBX Authentication Bypass VulnerabilitySangoma FreePBX contains an authentication bypass vulnerability due to insufficiently sanitized user-supplied data allows unauthenticated access to FreePBX Administrator leading to arbitrary database manipulation and remote code execution.
|
|
|
| CVE-2025-7775 CWE-119 | Citrix NetScaler Registro y acción publicados por CISACitrix NetScaler Memory Overflow VulnerabilityCitrix NetScaler ADC and NetScaler Gateway contain a memory overflow vulnerability that could allow for remote code execution and/or denial of service.
|
|
|
| CVE-2024-8068 CWE-269 | Citrix Session Recording Registro y acción publicados por CISACitrix Session Recording Improper Privilege Management VulnerabilityCitrix Session Recording contains an improper privilege management vulnerability that could allow for privilege escalation to NetworkService Account access. An attacker must be an authenticated user in the same Windows Active Directory domain as the session recording server domain.
|
|
|
| CVE-2024-8069 CWE-502 | Citrix Session Recording Registro y acción publicados por CISACitrix Session Recording Deserialization of Untrusted Data VulnerabilityCitrix Session Recording contains a deserialization of untrusted data vulnerability that allows limited remote code execution with privilege of a NetworkService Account access. Attacker must be an authenticated user on the same intranet as the session recording server.
|
|
|
| CVE-2025-48384 CWE-59, CWE-436 | Git Git Registro y acción publicados por CISAGit Link Following VulnerabilityGit contains a link following vulnerability that stems from Git’s inconsistent handling of carriage return characters in configuration files.
|
|
|
| CVE-2025-43300 CWE-787 | Apple iOS, iPadOS, and macOS Registro y acción publicados por CISAApple iOS, iPadOS, and macOS Out-of-Bounds Write VulnerabilityApple iOS, iPadOS, and macOS contain an out-of-bounds write vulnerability in the Image I/O framework.
|
|
|
| CVE-2025-54948 CWE-78 | Trend Micro Apex One Registro y acción publicados por CISATrend Micro Apex One OS Command Injection VulnerabilityTrend Micro Apex One Management Console (on-premise) contains an OS command injection vulnerability that could allow a pre-authenticated remote attacker to upload malicious code and execute commands on affected installations.
|
|
|
| CVE-2025-8875 | N-able N-Central Registro y acción publicados por CISAN-able N-Central Insecure Deserialization VulnerabilityN-able N-Central contains an insecure deserialization vulnerability that could lead to command execution.
|
|
|
| CVE-2025-8876 | N-able N-Central Registro y acción publicados por CISAN-able N-Central Command Injection VulnerabilityN-able N-Central contains a command injection vulnerability via improper sanitization of user input.
|
|
|
| CVE-2007-0671 | Microsoft Office Registro y acción publicados por CISAMicrosoft Office Excel Remote Code Execution VulnerabilityMicrosoft Office Excel contains a remote code execution vulnerability that can be exploited when a specially crafted Excel file is opened. This malicious file could be delivered as an email attachment or hosted on a malicious website. An attacker could leverage this vulnerability by creating a specially crafted Excel file, which, when opened, allowing an attacker to execute remote code on the affected system.
|
|
|
| CVE-2013-3893 CWE-399 | Microsoft Internet Explorer Registro y acción publicados por CISAMicrosoft Internet Explorer Resource Management Errors VulnerabilityMicrosoft Internet Explorer contains a memory corruption vulnerability that allows for remote code execution. The impacted products could be end-of-life (EoL) and/or end-of-service (EoS). Users should discontinue product utilization.
|
|
|
| CVE-2025-8088 CWE-35 | RARLAB WinRAR Registro y acción publicados por CISARARLAB WinRAR Path Traversal VulnerabilityRARLAB WinRAR contains a path traversal vulnerability affecting the Windows version of WinRAR. This vulnerability could allow an attacker to execute arbitrary code by crafting malicious archive files.
|
|
|
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
