참고 자료 · 23

취약점의 우선순위를 정하고 해결 방안을 검증합니다.

알려진 악용 사례, 노출된 자산, 비즈니스 영향 및 작동하는 수정 사항에 대한 증거를 연결합니다.

업데이트됨 · 20 min

권고문, 자산 목록, 수정 증거를 각각 별도 트레이에 둔 가상의 무인 사이버 관측실 AI로 생성한 편집용 일러스트

이 가이드가 달성하는 목표

  • 경고를 자산과 연결합니다.
  • 실제 긴급도를 순위화합니다.
  • 안전하게 배포합니다.
  • 검증 및 종료합니다.

빠른 확인

  • 영향을 받는 제품 및 버전이 실제로 배포되었습니까?
  • 자산에 접근 가능하고 비즈니스에 중요한 자산입니까?
  • 악용 사례가 문서화되었습니까?
  • 패치 적용 전 서비스를 보호하는 방법은 무엇입니까?
  • 자산에서 문제가 해결되었는지 확인하는 검사가 수행되었습니까?

단계별 방법

  1. 1

    인벤토리를 통합합니다.

    서비스, 제품, 버전, 환경, 노출 정도 및 소유자를 매핑합니다. 구성 요소 권고만으로는 취약한 인스턴스가 배포되었음을 입증할 수 없습니다.

    결과물: 날짜가 표시된 영향받는 자산 목록 및 불확실성.

  2. 2

    발견 사항 검증

    공급업체 권고 사항, CVE 식별자, 악용 조건 및 관련이 있는 경우 CISA의 알려진 악용 취약점 카탈로그를 비교합니다. 각 소스를 확인한 시점을 기록합니다.

    결과물: 주요 참조 자료가 포함된 발견 사항

  3. 3

    합리적인 우선순위 설정

    알려진 악용, 자산 접근성, 필요한 권한, 처리되는 데이터, 서비스 영향 및 사용 가능한 해결 방안을 고려합니다. 담당자와 상황별 마감일을 지정합니다.

    결과물: 우선순위 결정 근거

  4. 4

    변경 준비

    종속성, 변경 기간, 백업 및 롤백을 매핑합니다. 업데이트를 즉시 적용할 수 없는 경우 임시 제어 및 만료일을 기록합니다.

    결과물: 배포 계획 및 제한적 예외 사항

  5. 5

    배포 및 테스트

    승인된 프로세스를 사용하여 공급업체 수정 또는 완화 조치를 적용합니다. 결과 버전, 비즈니스 여정 및 회귀할 수 있는 통합을 확인하십시오.

    산출물: 배포 기록 및 기능 결과.

  6. 6

    종료 확인

    적절한 방법으로 실제 자산을 확인하고 누락된 인스턴스를 찾아 예외 사항을 재검토하십시오. 업데이트가 예약되었다는 이유만으로 티켓을 닫지 마십시오.

    산출물: 확인 증거 및 업데이트된 등록부. 산출물: 배포 기록 및 기능 결과. 종료 확인 적절한 방법으로 실제 자산을 확인하고 누락된 인스턴스를 찾아 예외 사항을 재검토하십시오. 업데이트가 예약되었다는 이유만으로 티켓을 닫지 마십시오.

관리 지표

지표측정 대상첫 번째 조치
범위알려진 버전과 소유자가 있는 중요 자산인벤토리 완료
지연검증부터 수정 확인까지의 시간반복되는 병목 현상 제거
검증실제 자산에서 수정 사항 재테스트증거 없이 폐쇄 재개
예외제어, 소유자 및 만료일이 있는 면제만료된 예외 종료

일반적인 실수

  • 자산 확인 없이 일반 점수만으로 순위 지정
  • KEV 목록이 있다고 해서 해당 제품이 자산에 존재한다고 가정
  • 서비스 동작 테스트 없이 배포
  • 검토 날짜 없이 보완 제어 남겨두기

자주 묻는 질문

가장 높은 점수를 받은 CVE가 항상 먼저 적용되어야 합니까?

점수는 기술적 심각도를 나타냅니다. 알려진 악용, 노출 및 로컬 서비스 영향은 운영 순서를 결정하는 데 도움이 됩니다.

패치가 없는 경우 어떻게 해야 하나요?

공급업체 완화 조치를 따르고, 가능한 한 노출을 줄이며, 담당자, 검토 날짜 및 잔여 위험을 문서화합니다.

작업은 언제 종료되나요?

영향을 받는 인스턴스에서 버전 또는 완화 조치가 검증되고 중요 기능이 테스트된 후 종료됩니다.

참고 자료: 데이터, 용도와 한계

문서 검토일 .

이 언어판의 상세 참고 설명은 영어로 제공됩니다.

Vulnerability: three complementary viewsCVE · Identify. CVSS · Technical severity. EPSS · Probability. KEV · Known exploitation. Affected version and product. Score from 0.0 to 10.0. 30-day horizon. Official CISA catalogue. Local decision: exposure, impact, evidence and remediation checks.Vulnerability: three complementary viewsCVE · IdentifyAffected version and productCVSS · Technical severityScore from 0.0 to 10.0EPSS · Probability30-day horizonKEV · Known exploitationOfficial CISA catalogueLocal decision: exposure, impact, evidence and remediation checks
Vulnerability: three complementary views
참고 자료: 데이터, 용도와 한계
출처와 목적확인된 데이터 또는 기준사용 방법유지해야 할 한계
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 distinct signals for a local decision
Four distinct signals for a local decision 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. CVSS · Severity Metrics and vector Version and author EPSS · Probability Thirty-day horizon Separate date and rank KEV · Known exploitation Product and requested action Catalogue edition VEX · Applicability Issuer, product and time Status and justification Local decision: deployed asset, exposure, consequences, owner and evidence.

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

Four questions and four kinds of information
SourceUseful questionWhat it cannot establish alone
CVSS 4.0What is the technical severity under the assessed metrics?The score proves neither exploitation nor consequences for your service.
EPSSWhat 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 KEVIs the vulnerability listed as known to be exploited?Listing does not establish that the product exists in your estate; absence does not establish safety.
VEXWhat 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.

CVSS 4.0: preserve groups, vector and assessment author
GroupRoleReading check
BaseIntrinsic vulnerability characteristics.A supplier’s CVSS-B is not your priority decision.
ThreatThreat characteristics that can change over time.Date the assessment and explain exploitation information used.
EnvironmentalCharacteristics specific to the consumer’s environment.State the controls and system importance considered rather than silently changing a score.
SupplementalAdditional 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.

EPSS: probability, percentile and missing data
Fictional exampleProvided valuesCorrect reading
A probabilityProbability : 0.05 · Percentile : Unspecified0.05 means a 5% estimated probability of observed exploitation within the model horizon, rather than an estate compromise rate.
Probability and rankProbability : 0.02 · Percentile : 0.97In 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 valueProbability : Unspecified · Percentile : UnspecifiedMissing 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.

Seven useful readings of the KEV schema
FieldsMeaningProposed check
catalogVersion / dateReleasedCatalogue version and publication time.Keep a reference to the consulted edition; distinguish publication time from your assessment time.
cveID / vendorProject / productIdentifier and product associated with the entry.Match name, version, distribution and embedded components before declaring an asset affected.
dateAddedDate the vulnerability entered the catalogue.Do not present it as the first exploitation date or CVE publication date.
requiredActionRequested action to address the vulnerability.Read the complete instruction and supplier references, then document local implementation.
dueDateCatalogue deadline for the requested action.Check the context and scope of the CISA instruction before adopting it as a local deadline.
knownRansomwareCampaignUseKnown indicates confirmed ransomware campaign use; Unknown means CISA lacks confirmation.Do not translate Unknown into never used or a definite false value.
cwesWeakness 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

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

Six readings that prevent a misleading priority
Published fieldUseful readingConclusion to avoid
cveIDJoin sources discussing the same vulnerability.The identifier year does not date KEV inclusion.
vendorProject · productFind the vendor advisory and local inventory.A product name does not replace affected versions and configurations.
dateAddedDate the entry’s inclusion in this catalogue.Do not call it discovery or first-exploitation date.
dueDate · requiredActionRead the published action and deadline together.Do not turn the date into a universal obligation or proof of remediation.
knownRansomwareCampaignUsePreserve Known, Unknown or an absent field.Unknown is not No and does not remove the known exploitation signal underlying KEV.
forensicTriage · cwesSeparate 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.

연도별 목록 추가 건수

연도별 목록 추가 건수Each bar counts entries retained in this snapshot by the year of dateAdded. It is not a discovery year or an exploitation frequency. The first year starts at this snapshot’s earliest entry and the release year is incomplete; these totals are not an annual attack trend.311202155520221872023186202424520252852026
Each bar counts entries retained in this snapshot by the year of dateAdded. It is not a discovery year or an exploitation frequency. The first year starts at this snapshot’s earliest entry and the release year is incomplete; these totals are not an annual attack trend.
연도별 목록 추가 건수 · dateAdded
등록 연도항목
2021311
2022555
2023187
2024186
2025245
2026285

결과 : 1769 / 1769 · 페이지 9 / 71

CISA KEV 목록 살펴보기 · 2026.11.06
CVE공급업체 또는 프로젝트 · product등록일 / 항목에 기재된 기한랜섬웨어 캠페인에서 사용 / forensicTriage
CVE-2026-34197

CWE-20, CWE-94

Apache

ActiveMQ

CISA가 공개한 항목과 조치

Apache ActiveMQ Improper Input Validation Vulnerability

Apache ActiveMQ contains an improper input validation vulnerability that allows for code injection.

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
https://activemq.apache.org/security-advisories.data/CVE-2026-34197-announcement.txt ; https://nvd.nist.gov/vuln/detail/CVE-2026-34197

activemq.apache.org ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2009-0238

CWE-94

Microsoft

Office

CISA가 공개한 항목과 조치

Microsoft Office Remote Code Execution

Microsoft Office Excel contains a remote code execution vulnerability that could allow an attacker to take complete control of an affected system if a user opens a specially crafted Excel file that includes a malformed object.

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
https://learn.microsoft.com/en-us/security-updates/securitybulletins/2009/ms09-009 ; https://nvd.nist.gov/vuln/detail/CVE-2009-0238

learn.microsoft.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2026-32201

CWE-20

Microsoft

SharePoint Server

CISA가 공개한 항목과 조치

Microsoft SharePoint Server Improper Input Validation Vulnerability

Microsoft SharePoint Server contains an improper input validation vulnerability that allows an unauthorized attacker to perform spoofing over a network.

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2026-32201 ; https://nvd.nist.gov/vuln/detail/CVE-2026-32201

msrc.microsoft.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2012-1854

CWE-426

Microsoft

Visual Basic for Applications (VBA)

CISA가 공개한 항목과 조치

Microsoft Visual Basic for Applications Insecure Library Loading Vulnerability

Microsoft Visual Basic for Applications (VBA) contains an insecure library loading vulnerability that could allow for remote code execution.

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
https://learn.microsoft.com/en-us/security-updates/securitybulletins/2012/ms12-046 ; https://nvd.nist.gov/vuln/detail/CVE-2012-1854

learn.microsoft.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2020-9715

CWE-416

Adobe

Acrobat

CISA가 공개한 항목과 조치

Adobe Acrobat Use-After-Free Vulnerability

Adobe Acrobat contains a use-after-free vulnerability that allows for code execution

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
https://helpx.adobe.com/security/products/acrobat/apsb20-48.html ; https://nvd.nist.gov/vuln/detail/CVE-2020-9715

helpx.adobe.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2023-21529

CWE-502

Microsoft

Exchange Server

CISA가 공개한 항목과 조치

Microsoft Exchange Server Deserialization of Untrusted Data Vulnerability

Microsoft Exchange Server contains a deserialization of untrusted data that allows an authenticated attacker to achieve remote code execution.

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-21529 ; https://nvd.nist.gov/vuln/detail/CVE-2023-21529

msrc.microsoft.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Known
forensicTriage
No
CVE-2023-36424

CWE-125

Microsoft

Windows

CISA가 공개한 항목과 조치

Microsoft Windows Out-of-Bounds Read Vulnerability

Microsoft Windows Common Log File System Driver contains an out-of-bounds read vulnerability that could allow a threat actor for privileges escalation

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
https://msrc.microsoft.com/update-guide/en-US/advisory/CVE-2023-36424 ; https://nvd.nist.gov/vuln/detail/CVE-2023-36424

msrc.microsoft.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2025-60710

CWE-59

Microsoft

Windows

CISA가 공개한 항목과 조치

Microsoft Windows Link Following Vulnerability

Microsoft Windows contains a link following vulnerability that allows for privilege escalation

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-60710 ; https://nvd.nist.gov/vuln/detail/CVE-2025-60710

msrc.microsoft.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Known
forensicTriage
No
CVE-2026-21643

CWE-89

Fortinet

FortiClient EMS

CISA가 공개한 항목과 조치

Fortinet FortiClient EMS SQL Injection Vulnerability

Fortinet FortiClient EMS contains a SQL injection vulnerability that may allow an unauthenticated attacker to execute unauthorized code or commands via specifically crafted HTTP requests.

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
https://fortiguard.fortinet.com/psirt/FG-IR-25-1142 ; https://nvd.nist.gov/vuln/detail/CVE-2026-21643

fortiguard.fortinet.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2026-34621

CWE-1321

Adobe

Acrobat and Reader

CISA가 공개한 항목과 조치

Adobe Acrobat and Reader Prototype Pollution Vulnerability

Adobe Acrobat and Reader contain a prototype pollution vulnerability that allows for arbitrary code execution.

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
https://helpx.adobe.com/security/products/acrobat/apsb26-43.html ; https://nvd.nist.gov/vuln/detail/CVE-2026-34621

helpx.adobe.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2026-1340

CWE-94

Ivanti

Endpoint Manager Mobile (EPMM)

CISA가 공개한 항목과 조치

Ivanti Endpoint Manager Mobile (EPMM) Code Injection Vulnerability

Ivanti Endpoint Manager Mobile (EPMM) contains a code injection vulnerability that could allow attackers to achieve unauthenticated remote code execution.

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
Please adhere to Ivanti's guidelines to assess exposure and mitigate risks. Check for signs of potential compromise on all internet accessible Ivanti products affected by this vulnerability. Apply any final mitigations provided by the vendor as soon as possible. For more information please see: https://hub.ivanti.com/s/article/Security-Advisory-Ivanti-Endpoint-Manager-Mobile-EPMM-CVE-2026-1281-CVE-2026-1340?language=en_US ; https://support.mobileiron.com/mi/vsp/AB1786671/ivanti-security-update-1761642-1.1.0S-5.noarch.rpm ; https://support.mobileiron.com/mi/vsp/AB1786671/ivanti-security-update-1761642-1.1.0L-5.noarch.rpm ; https://nvd.nist.gov/vuln/detail/CVE-2026-1340

hub.ivanti.com ↗

support.mobileiron.com ↗

support.mobileiron.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2026-35616

CWE-284

Fortinet

FortiClient EMS

CISA가 공개한 항목과 조치

Fortinet FortiClient EMS Improper Access Control Vulnerability

Fortinet FortiClient EMS contains an improper access control vulnerability that may allow an unauthenticated attacker to execute unauthorized code or commands via crafted requests.

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
Please adhere to Fortinet's guidelines to assess exposure and mitigate risks. Check for signs of potential compromise on all internet accessible Fortinet products affected by this vulnerability. Apply any final mitigations provided by the vendor as soon as they become available. For more information please see: https://fortiguard.fortinet.com/psirt/FG-IR-26-099 ; https://nvd.nist.gov/vuln/detail/CVE-2026-35616

fortiguard.fortinet.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2026-3502

CWE-494

TrueConf

Client

CISA가 공개한 항목과 조치

TrueConf Client Download of Code Without Integrity Check Vulnerability

TrueConf Client contains a download of code without integrity check vulnerability. An attacker who is able to influence the update delivery path can substitute a tampered update payload. If the payload is executed or installed by the updater, this may result in arbitrary code execution in the context of the updating process or user.

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
https://trueconf.com/blog/update/trueconf-8-5 ; https://trueconf.com/downloads/windows.html ; https://nvd.nist.gov/vuln/detail/CVE-2026-3502

trueconf.com ↗

trueconf.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2026-5281

CWE-416

Google

Dawn

CISA가 공개한 항목과 조치

Google Dawn Use-After-Free Vulnerability

Google Dawn contains an use-after-free vulnerability that could allow a remote attacker who had compromised the renderer process to execute arbitrary code via a crafted HTML page. This vulnerability could affect multiple Chromium-based products including, but not limited to, Google Chrome, Microsoft Edge, and Opera.

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
This vulnerability affects an open-source component, third-party library, protocol, or proprietary implementation that could be used by different products. For more information, please see: https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_31.html ; https://nvd.nist.gov/vuln/detail/CVE-2026-5281

chromereleases.googleblog.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2026-3055

CWE-125

Citrix

NetScaler

CISA가 공개한 항목과 조치

Citrix NetScaler Out-of-Bounds Read Vulnerability

Citrix NetScaler ADC (formerly Citrix ADC), NetScaler Gateway (formerly Citrix Gateway) and NetScaler ADC FIPS and NDcPP contain an out-of-bounds reads vulnerability when configured as a SAML IDP leading to memory overread.

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
https://support.citrix.com/support-home/kbsearch/article?articleNumber=CTX696300&articleURL=NetScaler_ADC_and_NetScaler_Gateway_Security_Bulletin_for_CVE_2026_3055_and_CVE_2026_4368 ; https://nvd.nist.gov/vuln/detail/CVE-2026-3055

support.citrix.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2025-53521

CWE-121

F5

BIG-IP

CISA가 공개한 항목과 조치

F5 BIG-IP Stack-Based Buffer Overflow Vulnerability

F5 BIG-IP APM contains a stack-based buffer overflow vulnerability that could allow a threat actor to achieve remote code execution.

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
Please adhere to F5’s guidelines to assess exposure and mitigate risks. Check for signs of potential compromise on all internet accessible F5 products affected by this vulnerability. For more information please see: https://my.f5.com/manage/s/article/K000156741 ; https://my.f5.com/manage/s/article/K000160486 ; https://my.f5.com/manage/s/article/K11438344 ; https://nvd.nist.gov/vuln/detail/CVE-2025-53521

my.f5.com ↗

my.f5.com ↗

my.f5.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2026-33634

CWE-506

Aquasecurity

Trivy

CISA가 공개한 항목과 조치

Aquasecurity Trivy Embedded Malicious Code Vulnerability

Aquasecurity Trivy contains an embedded malicious code vulnerability that could allow an attacker to gain access to everything in the CI/CD environment, including all tokens, SSH keys, cloud credentials, database passwords, and any sensitive configuration in memory.

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
This vulnerability involves a supply‑chain compromise in a product that may be used across multiple products and environments. Additional vendor‑provided guidance must be followed to ensure full remediation. For more information, please see: https://github.com/advisories/GHSA-69fq-xp46-6x23 ; https://nvd.nist.gov/vuln/detail/CVE-2026-33634

github.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2026-33017

CWE-94, CWE-95, CWE-306

Langflow

Langflow

CISA가 공개한 항목과 조치

Langflow Code Injection Vulnerability

Langflow contains a code injection vulnerability that could allow building public flows without requiring authentication.

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
https://github.com/langflow-ai/langflow/security/advisories/GHSA-vwmf-pq79-vjvx ; https://nvd.nist.gov/vuln/detail/CVE-2026-33017

github.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2025-31277

CWE-119

Apple

Multiple Products

CISA가 공개한 항목과 조치

Apple Multiple Products Buffer Overflow Vulnerability

Apple Safari, iOS, watchOS, visionOS, iPadOS, macOS, and tvOS contain a buffer overflow vulnerability that could allow the processing of maliciously crafted web content which may lead to memory corruption.

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
https://support.apple.com/en-us/124147 ; https://support.apple.com/en-us/124149 ; https://support.apple.com/en-us/124152 ; https://support.apple.com/en-us/124153 ; https://support.apple.com/en-us/124155 ; https://nvd.nist.gov/vuln/detail/CVE-2025-31277

support.apple.com ↗

support.apple.com ↗

support.apple.com ↗

support.apple.com ↗

support.apple.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2025-32432

CWE-94

Craft CMS

Craft CMS

CISA가 공개한 항목과 조치

Craft CMS Code Injection Vulnerability

Craft CMS contains a code injection vulnerability that allows a remote attacker to execute arbitrary code.

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
https://craftcms.com/knowledge-base/craft-cms-cve-2025-32432 ; https://github.com/craftcms/cms/security/advisories/GHSA-f3gw-9ww9-jmc3 ; https://nvd.nist.gov/vuln/detail/CVE-2025-32432

craftcms.com ↗

github.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2025-43510

CWE-667

Apple

Multiple Products

CISA가 공개한 항목과 조치

Apple Multiple Products Improper Locking Vulnerability

Apple watchOS, iOS, iPadOS, macOS, visionOS, and tvOS contain an improper locking vulnerability that could allow a malicious application to cause unexpected changes in memory shared between processes.

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
https://support.apple.com/en-us/125632 ; https://support.apple.com/en-us/125633 ; https://support.apple.com/en-us/125634 ; https://support.apple.com/en-us/125635 ; https://support.apple.com/en-us/125636 ; https://support.apple.com/en-us/125637 ; https://support.apple.com/en-us/125638 ; https://support.apple.com/en-us/125639 ; https://nvd.nist.gov/vuln/detail/CVE-2025-43510

support.apple.com ↗

support.apple.com ↗

support.apple.com ↗

support.apple.com ↗

support.apple.com ↗

support.apple.com ↗

support.apple.com ↗

support.apple.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2025-43520

CWE-120

Apple

Multiple Products

CISA가 공개한 항목과 조치

Apple Multiple Products Classic Buffer Overflow Vulnerability

Apple watchOS, iOS, iPadOS, macOS, visionOS, and tvOS contain a classic buffer overflow vulnerability which could allow a malicious application to cause unexpected system termination or write kernel memory.

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
https://support.apple.com/en-us/125632 ; https://support.apple.com/en-us/125633 ; https://support.apple.com/en-us/125634 ; https://support.apple.com/en-us/125635 ; https://support.apple.com/en-us/125636 ; https://support.apple.com/en-us/125637 ; https://support.apple.com/en-us/125638 ; https://support.apple.com/en-us/125639 ; https://nvd.nist.gov/vuln/detail/CVE-2025-43520

support.apple.com ↗

support.apple.com ↗

support.apple.com ↗

support.apple.com ↗

support.apple.com ↗

support.apple.com ↗

support.apple.com ↗

support.apple.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2025-54068

CWE-94

Laravel

Livewire

CISA가 공개한 항목과 조치

Laravel Livewire Code Injection Vulnerability

Laravel Livewire contain a code injection vulnerability that could allow unauthenticated attackers to achieve remote command execution in specific scenarios.

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
https://github.com/livewire/livewire/security/advisories/GHSA-29cq-5w36-x7w3 ; https://github.com/livewire/livewire/commit/ef04be759da41b14d2d129e670533180a44987dc ; https://nvd.nist.gov/vuln/detail/CVE-2025-54068

github.com ↗

github.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2026-20131

CWE-502

Cisco

Secure Firewall Management Center (FMC)

CISA가 공개한 항목과 조치

Cisco Secure Firewall Management Center (FMC) Software and Cisco Security Cloud Control (SCC) Firewall Management Deserialization of Untrusted Data Vulnerability

Cisco Secure Firewall Management Center (FMC) Software and Cisco Security Cloud Control (SCC) Firewall Management contain a deserialization of untrusted data vulnerability in the web-based management interface that could allow an unauthenticated, remote attacker to execute arbitrary Java code as root on an affected device.

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-fmc-rce-NKhnULJh ; https://nvd.nist.gov/vuln/detail/CVE-2026-20131

sec.cloudapps.cisco.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Known
forensicTriage
No
CVE-2025-66376

CWE-79

Synacor

Zimbra Collaboration Suite (ZCS)

CISA가 공개한 항목과 조치

Synacor Zimbra Collaboration Suite (ZCS) Cross-Site Scripting Vulnerability

Synacor Zimbra Collaboration Suite (ZCS) contains a cross-site scripting vulnerability in the Classic UI where attackers could abuse Cascading Style Sheets (CSS) @import directives in email HTML.

requiredAction
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
notes
https://wiki.zimbra.com/wiki/Zimbra_Security_Advisories ; https://nvd.nist.gov/vuln/detail/CVE-2025-66376

wiki.zimbra.com ↗

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No

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

  1. 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.

  2. 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.

  3. Document the change

    Assign an owner, prepare rollback and verify dependencies. A mitigation remains a scoped measure with an explicit validity period.

  4. 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 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 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.

공식 참조

참조는 방법을 뒷받침합니다. 상황에 맞게 검사를 조정하십시오. 이는 인증이 아닙니다. 원본 참조 제목 및 소스 문서는 다른 언어로 작성되었을 수 있습니다.

참고 자료 확인일 .