Ресурсы · 23
Приоритизация уязвимостей и проверка устранения
Связь известных эксплойтов, уязвимых активов, влияния на бизнес и доказательство работоспособности исправления.
Обновлено · 9 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. |
Добавления в каталог по годам
| Год добавления | Записи |
|---|---|
| 2021 | 311 |
| 2022 | 555 |
| 2023 | 187 |
| 2024 | 186 |
| 2025 | 245 |
| 2026 | 285 |
Результаты : 1769 / 1769 · Страница 3 / 71
| CVE | Поставщик или проект · product | Дата добавления / Срок в записи | Использование в кампаниях вымогателей / forensicTriage |
|---|---|---|---|
| CVE-2026-93952 CWE-20 | Arista VeloCloud Orchestrator Запись и действие, опубликованные CISAArista VeloCloud Orchestrator Improper Input Validation VulnerabilityArista VeloCloud Orchestrator (VCO) on-prem contains an improper input validation vulnerability that may allow a remote attacker to access privileged internal functionality and impact the VCO host. Successful exploitation may compromise the confidentiality, integrity, and availability of the orchestrator and data managed by the orchestrator.
|
|
|
| CVE-2026-94127 CWE-122 | F5 BIG-IP APM Запись и действие, опубликованные CISAF5 BIG-IP APM Heap-based Buffer Overflow VulnerabilityF5 BIG-IP APM contains a heap-based buffer overflow vulnerability when access policy and an OAuth profile are configured on a virtual server. This vulnerability could allow an unauthenticated attacker to perform remote code execution.
|
|
|
| CVE-2026-7273 CWE-121 | Zyxel GS1900 Series Switches Запись и действие, опубликованные CISAZyxel GS1900 Series Switches Stack-Based Buffer Overflow VulnerabilityZyxel GS1900 series switches contain a stack-based buffer overflow vulnerability in the CGI program which could allow a LAN-based, unauthenticated attacker to exploit the flaw and potentially execute OS commands via a crafted HTTP request.
|
|
|
| CVE-2025-39682 CWE-754 | Linux Kernel Запись и действие, опубликованные CISALinux Kernel Improper Check for Unusual or Exceptional Conditions VulnerabilityLinux Kernel contains an improper check for unusual or exceptional conditions vulnerability in the TLS receive path which allows a zero-length record retrieved from the rx_list to bypass the intended recvmsg() record-type handling, potentially causing subsequent TLS records to be processed using incorrect zero-copy and queuing assumptions. The impacted product(s) could be end-of-life (EoL) and/or end-of-service (EoS). Users are advised to discontinue use and/or transition to a supported version.
|
|
|
| CVE-2025-39964 CWE-362 | Linux Kernel Запись и действие, опубликованные CISALinux Kernel Race Condition VulnerabilityLinux Kernel contains a race condition vulnerability which allows concurrent writes to the same AF_ALG socket causing data to be unpredictably interleaved and creating inconsistencies in the socket's internal state.
|
|
|
| CVE-2026-53266 CWE-787 | Linux Kernel Запись и действие, опубликованные CISALinux Kernel Out-of-Bounds Write VulnerabilityLinux Kernel contains an out-of-bounds write vulnerability in the ebtables SNAT target which allows an ARP sender hardware address rewrite to write directly into a nonlinear socket-buffer fragment backed by a splice-imported file page. The impacted product(s) could be end-of-life (EoL) and/or end-of-service (EoS). Users are advised to discontinue use and/or transition to a supported version.
|
|
|
| CVE-2026-58704 CWE-693 | Google Pixel Запись и действие, опубликованные CISAGoogle Pixel Improper Authorization VulnerabilityGoogle Pixel devices contain an improper authorization vulnerability in the cellular modem. A logic error may allow an attacker to bypass permission checks and escalate privileges.
|
|
|
| CVE-2026-76460 CWE-648 | Cisco Identity Services Engine Запись и действие, опубликованные CISACisco Identity Services Engine Incorrect Use of Privileged APIs VulnerabilityCisco Identity Services Engine (ISE) and Cisco ISE Passive Identity Connector (ISE-PIC) contain an incorrect use of privileged APIs vulnerability that could allow an unauthenticated, remote attacker to gain unauthorized access to the affected device by bypassing the web-based management interface.
|
|
|
| CVE-2026-87886 CWE-276 | Acronis Backup Запись и действие, опубликованные CISAAcronis Backup Incorrect Default Permissions VulnerabilityAcronis Backup plugin for cPanel & WHM and extension for Plesk contains an incorrect default permissions vulnerability that could allow for privilege escalation.
|
|
|
| CVE-2026-76461 CWE-89 | Cisco Secure Email Gateway Запись и действие, опубликованные CISACisco Secure Email Gateway SQL Injection VulnerabilityCisco AsyncOS software for Cisco Secure Email Gateway (SEG) contains a SQL injection vulnerability that could allow an unauthenticated, remote attacker to execute arbitrary commands with root privileges on the underlying operating system.
|
|
|
| CVE-2026-42016 CWE-863 | JFrog Artifactory Запись и действие, опубликованные CISAJFrog Artifactory Incorrect Authorization VulnerabilityJFrog Artifactory contains an incorrect authorization vulnerability that leads to a privilege escalation attack due to a validation check of the token signature/issuer and not the token’s scope.
|
|
|
| CVE-2026-42018 CWE-287 | JFrog Artifactory Запись и действие, опубликованные CISAJFrog Artifactory Improper Authentication VulnerabilityJFrog Artifactory contains an improper authentication vulnerability that could return an internal anonymous-user token to an unauthenticated caller when anonymous access is disabled, potentially exposing sensitive resources.
|
|
|
| CVE-2026-84869 CWE-269, CWE-862 | ConnectWise ScreenConnect Запись и действие, опубликованные CISAConnectWise ScreenConnect Improper Privilege Management and Missing Authorization VulnerabilityConnectWise ScreenConnect contains both an improper privilege management and missing authorization vulnerability that may allow an attacker to transfer and execute files through an active remote session without authorization or host confirmation.
|
|
|
| CVE-2026-85706 CWE-35 | GitLab Community Edition and Enterprise Edition Запись и действие, опубликованные CISAGitLab Community Edition and Enterprise Edition Path Traversal VulnerabilityGitLab Community Edition and Enterprise Edition contains a path traversal vulnerability that allows an unauthenticated user to read arbitrary files due to an improper path confinement and missing authentication enforcement in the repository commits API.
|
|
|
| CVE-2026-67277 CWE-306 | MikroTik RouterOS Запись и действие, опубликованные CISAMikroTik RouterOS Missing Authentication for Critical Function VulnerabilityMikroTik RouterOS contains a missing authentication for critical function vulnerability which allows kernel memory disclosure and denial of service in the btest service.
|
|
|
| CVE-2026-86060 CWE-88 | MikroTik RouterOS Запись и действие, опубликованные CISAMikroTik RouterOS Improper Neutralization of Argument Delimiters in a Command VulnerabilityMikroTik RouterOS contains an improper neutralization of argument delimiters in a command vulnerability which allows an attacker to change the trusted RouterOS policy mask, leading to privilege escalation.
|
|
|
| CVE-2025-25249 CWE-122, CWE-787 | Fortinet Multiple Products Запись и действие, опубликованные CISAFortinet Multiple Products Heap-based Buffer Overflow VulnerabilityFortinet FortiOS, FortiSwitchManager, and FortiSASE contain a heap-based buffer overflow vulnerability that allows an attacker to execute unauthorized code or commands via specially crafted packets.
|
|
|
| CVE-2026-19490 CWE-288 | Citrix NetScaler Запись и действие, опубликованные CISACitrix NetScaler Authentication Bypass Using an Alternate Path or Channel VulnerabilityCitrix NetScaler ADC and NetScaler Gateway contain an authentication-bypass vulnerability involving an alternate path or channel. When the NetScaler appliance is configured as an AAA virtual server or as a Gateway (SSL VPN, ICA Proxy, CVPN, or RDP Proxy), an unauthenticated remote threat actor may be able to bypass authentication.
|
|
|
| CVE-2026-20079 CWE-288 | Cisco Secure Firewall Management Center (FMC) and Security Cloud Control (SCC) Firewall Management Запись и действие, опубликованные CISACisco Firewall Management Center Authentication Bypass Using an Alternate Path or Channel VulnerabilityCisco Secure Firewall Management Center (FMC) Software and Cisco Security Cloud Control (SCC) Firewall Management contain an authentication Bypass using an alternate path or channel vulnerability that could allow an unauthenticated, remote attacker to bypass authentication and execute script files on an affected device to obtain root access to the underlying operating system.
|
|
|
| CVE-2026-87491 CWE-787 | Google Chromium V8 Запись и действие, опубликованные CISAGoogle Chromium V8 Out of Bounds Write VulnerabilityGoogle Chromium V8 contains an out of bounds write vulnerability that allows a remote attacker to execute arbitrary code inside the sandbox 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-2026-75650 CWE-1336 | Adobe Commerce and Magento Запись и действие, опубликованные CISAAdobe Commerce and Magento Improper Neutralization of Special Elements Used in a Template Engine VulnerabilityAdobe Commerce and Magento Open Source contain an improper neutralization of special elements used in a template engine vulnerability that could allow an attacker to execute arbitrary code.
|
|
|
| CVE-2026-81963 CWE-59, CWE-284 | Microsoft Windows Запись и действие, опубликованные CISAMicrosoft Windows Link Following VulnerabilityMicrosoft Windows Update Stack contains a link following vulnerability that allows a local attacker to escalate privileges locally up to SYSTEM.
|
|
|
| CVE-2026-85880 CWE-122, CWE-908 | Microsoft Windows Запись и действие, опубликованные CISAMicrosoft Windows Heap-Based Buffer Overflow VulnerabilityMicrosoft Windows Advanced Local Procedure Call contains a heap-based buffer overflow vulnerability that allows an attacker to elevate privileges locally.
|
|
|
| CVE-2026-86218 CWE-96 | N-able N-central Запись и действие, опубликованные CISAN-able N-central Static Code Injection VulnerabilityN-able N-central contains a static code injection vulnerability that could allow for pre-authentication remote code execution.
|
|
|
| CVE-2026-85046 CWE-843 | Google Chromium V8 Запись и действие, опубликованные CISAGoogle Chromium V8 Type Confusion VulnerabilityGoogle Chromium V8 contains a type confusion vulnerability that allows a remote attacker to execute arbitrary code inside the sandbox 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.
|
|
|
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
