资源 · 23
确定漏洞优先级并验证修复情况
关联已知漏洞利用、暴露资产、业务影响和有效修复的证明。
已更新 · 19 min
本指南有助于实现的目标
- 将告警与资产匹配
- 对实际紧急程度进行排序
- 安全部署
- 验证并关闭
快速检查
- 受影响的产品和版本是否已实际部署?
- 该资产是否可访问且对业务至关重要?
- 是否已记录漏洞利用情况?
- 在应用补丁之前,有哪些措施保护服务?
- 检查是否确认问题已从资产中消除?
分步指南
- 1
整合清单
映射服务、产品、版本、环境、风险敞口和所有者。 仅凭组件建议无法证明存在易受攻击的实例。
交付成果:包含日期的受影响资产列表及不确定性。
- 2
确定发现结果
对比供应商建议、CVE 标识符、利用条件以及(如适用)CISA 的已知已利用漏洞目录。 记录每个来源的检查时间。
交付成果:包含主要参考资料的发现结果。
- 3
设定合理的优先级
考虑已知的利用方式、资产可达性、所需权限、处理的数据、服务影响以及可用的补救措施。 指定负责人并设定具体情况的截止日期。
交付成果:合理的优先级决策。
- 4
准备变更
映射依赖关系、变更窗口、备份和回滚。 如果无法及时应用更新,请记录临时控制措施及其失效日期。
交付成果:部署计划和有限的例外情况。
- 5
部署和测试
使用已批准的流程应用供应商提供的修复或缓解措施。 检查最终版本、业务流程以及可能出现倒退的集成。
交付成果:部署记录和功能结果。
- 6
验证关闭情况。
使用合适的方法检查实际资产,查找遗漏的实例并重新检查异常情况。 不要仅仅因为计划了更新就关闭工单。
交付成果:验证证据和更新后的注册表。
管理指标
| 指标 | 衡量内容 | 首要行动 |
|---|---|---|
| 覆盖面 | 已知版本和所有者的关键资产 | 完成清单 |
| 延迟 | 从资格认定到验证修复的时间 | 消除重复出现的瓶颈 |
| 验证 | 在真实资产上重新测试修复程序 | 在没有证据的情况下重新打开已关闭的修复程序 |
| 例外情况 | 具有控制权、所有者和到期日的豁免 | 关闭已过期的例外情况 |
常见错误
- 仅根据通用评分进行排名而不检查资产
- 假设关键事件漏洞 (KEV) 列表意味着该产品已存在于您的环境中
- 未测试服务行为就进行部署
- 未设置审查日期就保留补偿控制措施
常见问题解答
是否必须始终优先处理得分最高的 CVE?
评分描述技术严重性;已知的利用方式、暴露情况和本地服务影响指导您的操作顺序。
如果没有补丁怎么办?
遵循供应商的缓解措施,尽可能降低风险敞口,并记录负责人、审查日期和剩余风险。
何时结束这项工作?
在受影响的实例上验证版本或缓解措施,并测试关键功能后。
参考资料:数据、用途与局限
文档核查日期 .
此语言版本的详细参考说明以英语提供。
| 来源与目的 | 已核实的数据或指标 | 使用方法 | 需要保留的局限 |
|---|---|---|---|
| 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 与 VEX
此语言版本的详细参考说明以英语提供。
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
构建签名与来源
此语言版本的详细参考说明以英语提供。
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
浏览 CISA KEV 目录
此语言版本的详细参考说明以英语提供。
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.
- 记录
- 1769
- 不同的供应商/项目标签
- 291
- 目录发布时间
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. |
按年份统计的目录新增记录
结果 : 311 / 1769 · 页 7 / 13
| CVE | 供应商或项目 · product | 收录日期 / 记录中的截止日期 | 在勒索软件活动中的使用 / forensicTriage |
|---|---|---|---|
| CVE-2020-16017 CWE-416 | Google Chrome CISA 发布的记录与行动Google Chrome Use-After-Free VulnerabilityGoogle Chrome contains a use-after-free vulnerability that allows a remote attacker, who has compromised the renderer process, to potentially perform a sandbox escape via a crafted HTML page.
|
|
|
| CVE-2020-16846 CWE-78 | SaltStack Salt CISA 发布的记录与行动SaltStack Salt Shell Injection VulnerabilitySaltStack Salt allows an unauthenticated user with network access to the Salt API to use shell injections to run code on the Salt API using the SSH client. This vulnerability affects any users running the Salt API.
|
|
|
| CVE-2020-17087 CWE-131 | Microsoft Windows CISA 发布的记录与行动Microsoft Windows Kernel Privilege Escalation VulnerabilityMicrosoft Windows kernel contains an unspecified vulnerability that allows for privilege escalation.
|
|
|
| CVE-2020-17144 CWE-502 | Microsoft Exchange Server CISA 发布的记录与行动Microsoft Exchange Server Remote Code Execution VulnerabilityMicrosoft Exchange Server improperly validates cmdlet arguments which allow an attacker to perform remote code execution.
|
|
|
| CVE-2020-17496 CWE-74 | vBulletin vBulletin CISA 发布的记录与行动vBulletin PHP Module Remote Code Execution VulnerabilityThe PHP module within vBulletin contains an unspecified vulnerability that allows for remote code execution via crafted subWidgets data in an ajax/render/widget_tabbedcontainer_tab_panel request. This CVE ID resolves an incomplete patch for CVE-2019-16759.
|
|
|
| CVE-2020-17530 CWE-917 | Apache Struts CISA 发布的记录与行动Apache Struts Remote Code Execution VulnerabilityForced Object-Graph Navigation Language (OGNL) evaluation in Apache Struts, when evaluated on raw user input in tag attributes, can lead to remote code execution.
|
|
|
| CVE-2020-24557 | Trend Micro Apex One, OfficeScan, and Worry-Free Business Security CISA 发布的记录与行动Trend Micro Multiple Products Improper Access Control VulnerabilityTrend Micro Apex One, OfficeScan, and Worry-Free Business Security on Microsoft Windows contain an improper access control vulnerability that may allow an attacker to manipulate a particular product folder to disable the security temporarily, abuse a specific Windows function, and attain privilege escalation.
|
|
|
| CVE-2020-25213 CWE-434 | WordPress File Manager Plugin CISA 发布的记录与行动WordPress File Manager Plugin Remote Code Execution VulnerabilityWordPress File Manager plugin contains a remote code execution vulnerability that allows unauthenticated users to execute PHP code and upload malicious files on a target site.
|
|
|
| CVE-2020-25506 CWE-78 | D-Link DNS-320 Device CISA 发布的记录与行动D-Link DNS-320 Device Command Injection VulnerabilityD-Link DNS-320 device contains a command injection vulnerability in the sytem_mgr.cgi component that may allow for remote code execution.
|
|
|
| CVE-2020-2555 CWE-502 | Oracle Multiple Products CISA 发布的记录与行动Oracle Multiple Products Remote Code Execution VulnerabilityMultiple Oracle products contain a remote code execution vulnerability that allows an unauthenticated attacker with network access via T3 or HTTP to takeover the affected system. Impacted Oracle products: Oracle Coherence in Fusion Middleware, Oracle Utilities Framework, Oracle Retail Assortment Planning, Oracle Commerce, Oracle Communications Diameter Signaling Router (DSR).
|
|
|
| CVE-2020-26919 | NETGEAR JGS516PE Devices CISA 发布的记录与行动Netgear JGS516PE Devices Missing Function Level Access Control VulnerabilityNetgear JGS516PE devices contain a missing function level access control vulnerability.
|
|
|
| CVE-2020-27930 CWE-787 | Apple Multiple Products CISA 发布的记录与行动Apple Multiple Products Memory Corruption VulnerabilityApple iOS, iPadOS, macOS, and watchOS FontParser contain a memory corruption vulnerability which may allow for code execution when processing maliciously crafted front.
|
|
|
| CVE-2020-27932 CWE-843 | Apple Multiple Products CISA 发布的记录与行动Apple Multiple Products Type Confusion VulnerabilityApple iOS, iPadOS, macOS, and watchOS contain a type confusion vulnerability that may allow a malicious application to execute code with kernel privileges.
|
|
|
| CVE-2020-27950 CWE-665 | Apple Multiple Products CISA 发布的记录与行动Apple Multiple Products Memory Initialization VulnerabilityApple iOS, iPadOS, macOS, and watchOS contain a memory initialization vulnerability that may allow a malicious application to disclose kernel memory.
|
|
|
| CVE-2020-29557 CWE-119 | D-Link DIR-825 R1 Devices CISA 发布的记录与行动D-Link DIR-825 R1 Devices Buffer Overflow VulnerabilityD-Link DIR-825 R1 devices contain a buffer overflow vulnerability in the web interface that may allow for remote code execution.
|
|
|
| CVE-2020-29583 CWE-522 | Zyxel Multiple Products CISA 发布的记录与行动Zyxel Multiple Products Use of Hard-Coded Credentials VulnerabilityZyxel firewalls (ATP, USG, VM) and AP Controllers (NXC2500 and NXC5500) contain a use of hard-coded credentials vulnerability in an undocumented account ("zyfwp") with an unchangeable password.
|
|
|
| CVE-2020-3118 CWE-134 | Cisco IOS XR CISA 发布的记录与行动Cisco IOS XR Software Discovery Protocol Format String VulnerabilityCisco IOS XR improperly validates string input from certain fields in Cisco Discovery Protocol messages. Exploitation could allow an unauthenticated, adjacent attacker to execute code with administrative privileges or cause a reload on an affected device.
|
|
|
| CVE-2020-3161 CWE-20 | Cisco Cisco IP Phones CISA 发布的记录与行动Cisco IP Phones Web Server Remote Code Execution and Denial-of-Service VulnerabilityCisco IP Phones contain an improper input validation vulnerability for HTTP requests. Exploitation could allow an attacker to execute code remotely with root privileges or cause a denial-of-service (DoS) condition.
|
|
|
| CVE-2020-3452 CWE-20 | Cisco Adaptive Security Appliance (ASA) and Firepower Threat Defense (FTD) CISA 发布的记录与行动Cisco ASA and FTD Read-Only Path Traversal VulnerabilityCisco Adaptive Security Appliance (ASA) and Firepower Threat Defense (FTD) contain an improper input validation vulnerability when HTTP requests process URLs. An attacker could exploit this vulnerability by sending a crafted HTTP request containing directory traversal character sequences to an affected device. A successful exploit could allow the attacker to view arbitrary files within the web services file system on the targeted device.
|
|
|
| CVE-2020-3566 CWE-400 | Cisco IOS XR CISA 发布的记录与行动Cisco IOS XR Software DVMRP Memory Exhaustion VulnerabilityCisco IOS XR Distance Vector Multicast Routing Protocol (DVMRP) incorrectly handles Internet Group Management Protocol (IGMP) packets. Exploitation could allow an unauthenticated, remote attacker to immediately crash the IGMP process or make it consume available memory and eventually crash.
|
|
|
| CVE-2020-3569 CWE-400 | Cisco IOS XR CISA 发布的记录与行动Cisco IOS XR Software DVMRP Memory Exhaustion VulnerabilityCisco IOS XR Distance Vector Multicast Routing Protocol (DVMRP) incorrectly handles Internet Group Management Protocol (IGMP) packets. Exploitation could allow an unauthenticated, remote attacker to immediately crash the IGMP process or make it consume available memory and eventually crash.
|
|
|
| CVE-2020-3580 CWE-79 | Cisco Adaptive Security Appliance (ASA) and Firepower Threat Defense (FTD) CISA 发布的记录与行动Cisco ASA and FTD Cross-Site Scripting (XSS) VulnerabilityCisco Adaptive Security Appliance (ASA) and Firepower Threat Defense (FTD) contain an insufficient input validation vulnerability for user-supplied input by the web services interface. Successful exploitation could allow an attacker to perform cross-site scripting (XSS) in the context of the interface or access sensitive browser-based information.
|
|
|
| CVE-2020-3950 CWE-269 | VMware Multiple Products CISA 发布的记录与行动VMware Multiple Products Privilege Escalation VulnerabilityVMware Fusion, Remote Console (VMRC) for Mac, and Horizon Client for Mac contain a privilege escalation vulnerability due to improper use of setuid binaries that allows attackers to escalate privileges to root.
|
|
|
| CVE-2020-3952 CWE-306 | VMware vCenter Server CISA 发布的记录与行动VMware vCenter Server Information Disclosure VulnerabilityVMware vCenter Server contains an information disclosure vulnerability in the VMware Directory Service (vmdir) when the Platform Services Controller (PSC) does not correctly implement access controls. Successful exploitation allows an attacker with network access to port 389 to extract sensitive information.
|
|
|
| CVE-2020-3992 CWE-416 | VMware ESXi CISA 发布的记录与行动VMware ESXi OpenSLP Use-After-Free VulnerabilityVMware ESXi OpenSLP contains a use-after-free vulnerability that allows an attacker residing in the management network with access to port 427 to perform 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.
参考资料详情 · CISA KEV
How we publish this official snapshot
此语言版本的详细参考说明以英语提供。
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.
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.
官方参考文献
参考文献支持该方法。 请根据您的实际情况调整检查;它们并非认证。 原始参考文献标题和源文档可能使用其他语言。
参考资料查阅日期 .
- 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
