Recursos · 23
Priorize as vulnerabilidades e verifique a remediação.
Conecte a exploração conhecida, os ativos expostos, o impacto nos negócios e a comprovação de uma correção funcional.
Atualizado · 9 min
O que este guia ajuda a alcançar
- Atribuir alertas aos ativos
- Classificar a urgência real
- Implementar com segurança
- Verificar e encerrar
Verificação rápida
- O produto e a versão afetados estão realmente implantados?
- O ativo é acessível e crítico para os negócios?
- A exploração está documentada?
- O que protege o serviço antes da aplicação de um patch?
- Uma verificação confirma que o problema foi corrigido no ativo?
Método passo a passo
- 1
Consolidar o inventário
Mapear serviços, produtos, versões, ambientes, exposição e proprietários. Um aviso de componente por si só não comprova que uma instância vulnerável está implantada.
Entregável: lista de ativos afetados com data e incertezas.
- 2
Qualificar a descoberta
Comparar o aviso do fornecedor, o identificador CVE, as condições de exploração e, quando relevante, o catálogo de vulnerabilidades exploradas conhecidas da CISA. Registrar quando cada fonte foi verificada.
Entregável: descoberta com referências primárias.
- 3
Definir uma prioridade defensável
Considerar a exploração conhecida, a acessibilidade do ativo, os privilégios necessários, os dados manipulados, o impacto no serviço e a remediação disponível. Atribuir um responsável e um prazo específico ao contexto.
Entregável: decisão de prioridade fundamentada.
- 4
Preparar a alteração
Mapear dependências, janela de alteração, backup e reversão. Se uma atualização não puder ser aplicada imediatamente, registrar o controle temporário e sua expiração.
Entregável: plano de implementação e exceção limitada.
- 5
Implantar e testar
Aplicar a correção ou mitigação do fornecedor usando o processo aprovado. Verificar a versão resultante, o fluxo de negócios e as integrações que podem regredir.
Entregável: registro de implantação e resultado funcional.
- 6
Verificar encerramento
Verificar o ativo real com um método adequado, encontrar instâncias ausentes e revisar exceções. Não fechar um chamado apenas porque uma atualização foi agendada.
Entregável: evidência de verificação e registro atualizado. ...4 Entregável: evidência de verificação e registro atualizado.
Indicadores de gestão
| Indicador | O que mede | Primeira ação |
|---|---|---|
| Abrangência | Ativos críticos com versões e proprietários conhecidos | Concluir o inventário |
| Atraso | Tempo desde a qualificação até a correção verificada | Remover gargalos recorrentes |
| Verificação | Correções retestadas em ativos reais | Reabrir encerramentos sem evidências |
| Exceções | Isenções com controle, proprietário e expiração | Fechar exceções expiradas |
Erros comuns
- Classificação baseada exclusivamente em uma pontuação genérica sem verificar o ativo
- Presumir que uma listagem de KEV significa que o produto existe em seu ambiente
- Implantação sem testar o comportamento do serviço
- Deixar controles compensatórios sem uma data de revisão
Perguntas frequentes
O CVE com a pontuação mais alta deve sempre vir primeiro?
Uma pontuação descreve a gravidade técnica; a exploração conhecida, a exposição e o impacto no serviço local orientam sua ordem operacional.
E se não houver patch disponível?
Siga as medidas de mitigação do fornecedor, reduza a exposição sempre que possível e documente o responsável, a data de revisão e o risco residual.
Quando o trabalho é considerado concluído?
Após a versão ou mitigação ter sido verificada nas instâncias afetadas e a funcionalidade crítica ter sido testada.
Referências: dados, usos e limites
Documentação consultada em .
As notas detalhadas desta edição estão disponíveis em inglês.
| Fonte e finalidade | Dado ou referência verificada | Como utilizar | Limite a preservar |
|---|---|---|---|
| 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
As notas detalhadas desta edição estão disponíveis em 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
Assinatura e origem do build
As notas detalhadas desta edição estão disponíveis em 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 o catálogo KEV da CISA
As notas detalhadas desta edição estão disponíveis em 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.
- Registos
- 1769
- Designações distintas de fornecedor/projeto
- 291
- Publicação do 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. |
Inclusões no catálogo por ano
| Ano de inclusão | Registos |
|---|---|
| 2021 | 311 |
| 2022 | 555 |
| 2023 | 187 |
| 2024 | 186 |
| 2025 | 245 |
| 2026 | 285 |
Resultados : 186 / 1769 · Página 2 / 8
| CVE | Fornecedor ou projeto · product | Data de inclusão / Prazo do registo | Uso em campanhas de ransomware / forensicTriage |
|---|---|---|---|
| CVE-2024-9463 CWE-78 | Palo Alto Networks Expedition Registo e ação publicados pela CISAPalo Alto Networks Expedition OS Command Injection VulnerabilityPalo Alto Networks Expedition contains an OS command injection vulnerability that allows an unauthenticated attacker to run arbitrary OS commands as root in Expedition, resulting in disclosure of usernames, cleartext passwords, device configurations, and device API keys of PAN-OS firewalls.
|
|
|
| CVE-2024-9465 CWE-89 | Palo Alto Networks Expedition Registo e ação publicados pela CISAPalo Alto Networks Expedition SQL Injection VulnerabilityPalo Alto Networks Expedition contains a SQL injection vulnerability that allows an unauthenticated attacker to reveal Expedition database contents, such as password hashes, usernames, device configurations, and device API keys. With this, attackers can also create and read arbitrary files on the Expedition system.
|
|
|
| CVE-2014-2120 CWE-79 | Cisco Adaptive Security Appliance (ASA) Registo e ação publicados pela CISACisco Adaptive Security Appliance (ASA) Cross-Site Scripting (XSS) VulnerabilityCisco Adaptive Security Appliance (ASA) contains a cross-site scripting (XSS) vulnerability in the WebVPN login page. This vulnerability allows remote attackers to inject arbitrary web script or HTML via an unspecified parameter.
|
|
|
| CVE-2021-26086 CWE-22 | Atlassian Jira Server and Data Center Registo e ação publicados pela CISAAtlassian Jira Server and Data Center Path Traversal VulnerabilityAtlassian Jira Server and Data Center contain a path traversal vulnerability that allows a remote attacker to read particular files in the /WEB-INF/web.xml endpoint.
|
|
|
| CVE-2021-41277 CWE-200 | Metabase Metabase Registo e ação publicados pela CISAMetabase GeoJSON API Local File Inclusion VulnerabilityMetabase contains a local file inclusion vulnerability in the custom map support in the API to read GeoJSON formatted data.
|
|
|
| CVE-2024-43451 CWE-73 | Microsoft Windows Registo e ação publicados pela CISAMicrosoft Windows NTLMv2 Hash Disclosure Spoofing VulnerabilityMicrosoft Windows contains an NTLMv2 hash spoofing vulnerability that could result in disclosing a user's NTLMv2 hash to an attacker via a file open operation. The attacker could then leverage this hash to impersonate that user.
|
|
|
| CVE-2024-49039 CWE-287 | Microsoft Windows Registo e ação publicados pela CISAMicrosoft Windows Task Scheduler Privilege Escalation VulnerabilityMicrosoft Windows Task Scheduler contains a privilege escalation vulnerability that can allow an attacker-provided, local application to escalate privileges outside of its AppContainer, and access privileged RPC functions.
|
|
|
| CVE-2019-16278 CWE-22 | Nostromo nhttpd Registo e ação publicados pela CISANostromo nhttpd Directory Traversal VulnerabilityNostromo nhttpd contains a directory traversal vulnerability in the http_verify() function in a non-chrooted nhttpd server allowing for remote code execution.
|
|
|
| CVE-2024-43093 | Android Framework Registo e ação publicados pela CISAAndroid Framework Privilege Escalation VulnerabilityAndroid Framework contains an unspecified vulnerability that allows for privilege escalation.
|
|
|
| CVE-2024-51567 CWE-276 | CyberPersons CyberPanel Registo e ação publicados pela CISACyberPanel Incorrect Default Permissions VulnerabilityCyberPanel contains an incorrect default permissions vulnerability that allows a remote, unauthenticated attacker to execute commands as root.
|
|
|
| CVE-2024-5910 CWE-306 | Palo Alto Networks Expedition Registo e ação publicados pela CISAPalo Alto Networks Expedition Missing Authentication VulnerabilityPalo Alto Networks Expedition contains a missing authentication vulnerability that allows an attacker with network access to takeover an Expedition admin account and potentially access configuration secrets, credentials, and other data.
|
|
|
| CVE-2024-8956 CWE-287 | PTZOptics PT30X-SDI/NDI Cameras Registo e ação publicados pela CISAPTZOptics PT30X-SDI/NDI Cameras Authentication Bypass VulnerabilityPTZOptics PT30X-SDI/NDI cameras contain an insecure direct object reference (IDOR) vulnerability that allows a remote, attacker to bypass authentication for the /cgi-bin/param.cgi CGI script. If combined with CVE-2024-8957, this can lead to remote code execution as root.
|
|
|
| CVE-2024-8957 CWE-78 | PTZOptics PT30X-SDI/NDI Cameras Registo e ação publicados pela CISAPTZOptics PT30X-SDI/NDI Cameras OS Command Injection VulnerabilityPTZOptics PT30X-SDI/NDI cameras contain an OS command injection vulnerability that allows a remote, authenticated attacker to escalate privileges to root via a crafted payload with the ntp_addr parameter of the /cgi-bin/param.cgi CGI script.
|
|
|
| CVE-2024-20481 CWE-772 | Cisco Adaptive Security Appliance (ASA) and Firepower Threat Defense (FTD) Registo e ação publicados pela CISACisco ASA and FTD Denial-of-Service VulnerabilityCisco Adaptive Security Appliance (ASA) and Firepower Threat Defense (FTD) contain a missing release of resource after effective lifetime vulnerability that could allow an unauthenticated, remote attacker to cause a denial-of-service (DoS) of the RAVPN service.
|
|
|
| CVE-2024-37383 CWE-79 | Roundcube Webmail Registo e ação publicados pela CISARoundCube Webmail Cross-Site Scripting (XSS) VulnerabilityRoundCube Webmail contains a cross-site scripting (XSS) vulnerability in the handling of SVG animate attributes that allows a remote attacker to run malicious JavaScript code.
|
|
|
| CVE-2024-47575 CWE-306 | Fortinet FortiManager Registo e ação publicados pela CISAFortinet FortiManager Missing Authentication VulnerabilityFortinet FortiManager contains a missing authentication vulnerability in the fgfmd daemon that allows a remote, unauthenticated attacker to execute arbitrary code or commands via specially crafted requests.
|
|
|
| CVE-2024-38094 CWE-502 | Microsoft SharePoint Registo e ação publicados pela CISAMicrosoft SharePoint Deserialization VulnerabilityMicrosoft SharePoint contains a deserialization vulnerability that allows for remote code execution.
|
|
|
| CVE-2024-9537 | ScienceLogic SL1 Registo e ação publicados pela CISAScienceLogic SL1 Unspecified VulnerabilityScienceLogic SL1 (formerly EM7) is affected by an unspecified vulnerability involving an unspecified third-party component.
|
|
|
| CVE-2024-40711 CWE-502 | Veeam Backup & Replication Registo e ação publicados pela CISAVeeam Backup and Replication Deserialization VulnerabilityVeeam Backup and Replication contains a deserialization vulnerability allowing an unauthenticated user to perform remote code execution.
|
|
|
| CVE-2024-28987 CWE-798 | SolarWinds Web Help Desk Registo e ação publicados pela CISASolarWinds Web Help Desk Hardcoded Credential VulnerabilitySolarWinds Web Help Desk contains a hardcoded credential vulnerability that could allow a remote, unauthenticated user to access internal functionality and modify data.
|
|
|
| CVE-2024-30088 CWE-367 | Microsoft Windows Registo e ação publicados pela CISAMicrosoft Windows Kernel TOCTOU Race Condition VulnerabilityMicrosoft Windows Kernel contains a time-of-check to time-of-use (TOCTOU) race condition vulnerability that could allow for privilege escalation.
|
|
|
| CVE-2024-9680 CWE-416 | Mozilla Firefox Registo e ação publicados pela CISAMozilla Firefox Use-After-Free VulnerabilityMozilla Firefox and Firefox ESR contain a use-after-free vulnerability in Animation timelines that allows for code execution in the content process.
|
|
|
| CVE-2024-23113 CWE-134 | Fortinet Multiple Products Registo e ação publicados pela CISAFortinet Multiple Products Format String VulnerabilityFortinet FortiOS, FortiPAM, FortiProxy, and FortiWeb contain a format string vulnerability that allows a remote, unauthenticated attacker to execute arbitrary code or commands via specially crafted requests.
|
|
|
| CVE-2024-9379 CWE-89 | Ivanti Cloud Services Appliance (CSA) Registo e ação publicados pela CISAIvanti Cloud Services Appliance (CSA) SQL Injection VulnerabilityIvanti Cloud Services Appliance (CSA) contains a SQL injection vulnerability in the admin web console in versions prior to 5.0.2, which can allow a remote attacker authenticated as administrator to run arbitrary SQL statements.
|
|
|
| CVE-2024-9380 CWE-77 | Ivanti Cloud Services Appliance (CSA) Registo e ação publicados pela CISAIvanti Cloud Services Appliance (CSA) OS Command Injection VulnerabilityIvanti Cloud Services Appliance (CSA) contains an OS command injection vulnerability in the administrative console which can allow an authenticated attacker with application admin privileges to pass commands to the underlying OS.
|
|
|
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.
Informação documental · CISA KEV
How we publish this official snapshot
As notas detalhadas desta edição estão disponíveis em 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 o catálogo e o 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.
Referências oficiais
As referências apoiam o método. Adapte as verificações ao seu contexto; elas não são uma certificação. Os títulos das referências originais e os documentos de origem podem estar em outro idioma.
Referências consultadas em .
- 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
