Ressourcen · 23

Priorisieren Sie Schwachstellen und überprüfen Sie deren Behebung

Verbinden Sie bekannte Ausnutzung, exponierte Vermögenswerte, geschäftliche Auswirkungen und den Nachweis einer funktionierenden Lösung.

Aktualisiert · 9 min

Fiktives Cyber-Observatorium mit getrennten Ablagen für Hinweise, Inventar und Behebungsnachweise, ohne Personen KI-generierte redaktionelle Illustration

Wozu dieser Leitfaden beiträgt

  • Zuordnung von Warnungen zu Assets
  • Rang tatsächliche Dringlichkeit
  • Sicher ausrollen
  • Überprüfen und schließen

Kurzcheck

  • Ist das betroffene Produkt und die betroffene Version tatsächlich im Einsatz?
  • Ist das Asset erreichbar und geschäftskritisch?
  • Ist die Ausnutzung dokumentiert?
  • Was schützt den Dienst vor einem Patch?
  • Bestätigt eine Überprüfung, dass das Problem bei der Anlage behoben ist?

Schritt-für-Schritt-Anleitung

  1. 1

    Konsolidieren Sie den Bestand

    Kartendienste, Produkte, Versionen, Umgebungen, Exposition und Besitzer. Eine Komponentenwarnung allein beweist nicht, dass eine anfällige Instanz bereitgestellt wird.

    Liefergegenstand: datierte Liste der betroffenen Anlagen und Unsicherheiten.

  2. 2

    Qualifizieren Sie den Befund

    Vergleichen Sie die Herstellerempfehlung, die CVE-Kennung, die Ausnutzungsbedingungen und gegebenenfalls den CISA-Katalog bekannter ausgenutzter Schwachstellen. Notieren Sie, wann jede Quelle überprüft wurde.

    Liefergegenstand: Befund mit primären Referenzen.

  3. 3

    Legen Sie eine vertretbare Priorität fest

    Berücksichtigen Sie bekannte Ausnutzung, Erreichbarkeit von Assets, erforderliche Berechtigungen, verarbeitete Daten, Auswirkungen auf Dienste und verfügbare Abhilfemaßnahmen. Weisen Sie einen Eigentümer und eine kontextspezifische Frist zu.

    Liefergegenstand: begründete Prioritätsentscheidung.

  4. 4

    Bereiten Sie die Änderung vor

    Abhängigkeiten zuordnen, Fenster ändern, Backup und Rollback. Wenn ein Update nicht zeitnah angewendet werden kann, notieren Sie die vorübergehende Kontrolle und deren Ablauf.

    Lieferinhalt: Rollout-Plan und begrenzte Ausnahme.

  5. 5

    Bereitstellen und testen

    Wenden Sie die Herstellerkorrektur oder -minderung mithilfe des genehmigten Prozesses an. Überprüfen Sie die resultierende Version, die Geschäftsreise und die Integrationen, bei denen es zu Rückschritten kommen kann.

    Liefergegenstand: Einsatzprotokoll und Funktionsergebnis.

  6. 6

    Abschluss überprüfen

    Überprüfen Sie das tatsächliche Asset mit einer geeigneten Methode, finden Sie fehlende Instanzen und prüfen Sie Ausnahmen erneut. Schließen Sie ein Ticket nicht, weil lediglich ein Update geplant war.

    Liefergegenstand: Verifizierungsnachweis und aktualisiertes Register.

Managementindikatoren

IndikatorWas es misstErste Aktion
AbdeckungKritische Assets mit bekannten Versionen und BesitzernVervollständigen Sie die Bestandsaufnahme
VerzögerungZeit von der Qualifizierung bis zum verifizierten FixWiederholte Engpässe beseitigen
VerifizierungKorrekturen wurden erneut an realen Vermögenswerten getestetWiederaufnahme von Schließungen ohne Beweise
AusnahmenVerzichtserklärungen mit Kontrolle, Eigentümer und AblaufAbgelaufene Ausnahmen schließen

Häufige Fallstricke

  • Ranking ausschließlich nach einem generischen Score ohne Prüfung des Assets
  • Angenommen, ein KEV-Eintrag bedeutet, dass das Produkt in Ihrem Bestand vorhanden ist
  • Bereitstellung ohne Testen des Dienstverhaltens
  • Kompensationskontrollen ohne Überprüfungsdatum belassen

Häufig gestellte Fragen

Muss der CVE mit der höchsten Punktzahl immer zuerst starten?

Ein Score beschreibt den technischen Schweregrad; Bekannte Ausnutzung, Gefährdung und lokale Serviceauswirkungen leiten Ihre Betriebsordnung.

Was ist, wenn kein Patch vorhanden ist?

Befolgen Sie die Abhilfemaßnahmen des Anbieters, reduzieren Sie die Gefährdung nach Möglichkeit und dokumentieren Sie einen Eigentümer, das Überprüfungsdatum und das Restrisiko.

Wann ist das Werk geschlossen?

Nachdem die Version oder Abhilfemaßnahme auf betroffenen Instanzen überprüft und kritische Funktionen getestet wurden.

Referenzen: Daten, Nutzung und Grenzen

Dokumentation geprüft am .

Ausführliche Hinweise stehen in dieser Ausgabe auf Englisch zur Verfügung.

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
Referenzen: Daten, Nutzung und Grenzen
Quelle und ZweckGeprüfte Daten oder RichtwertePraktische NutzungZu beachtende Grenze
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.

Methode vertiefen →

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.

Methode vertiefen →

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.

Methode vertiefen →

Absence from the catalogue does not establish safety. Administrative deadlines in it are not automatically binding on every organisation.

CVSS, EPSS, KEV und VEX

Ausführliche Hinweise stehen in dieser Ausgabe auf Englisch zur Verfügung.

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

Build-Signatur und Herkunft

Ausführliche Hinweise stehen in dieser Ausgabe auf Englisch zur Verfügung.

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-Katalog durchsuchen

Ausführliche Hinweise stehen in dieser Ausgabe auf Englisch zur Verfügung.

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.

Einträge
1769
Unterschiedliche Anbieter-/Projektbezeichnungen
291
Veröffentlichung des Katalogs

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.

Katalogaufnahmen nach Jahr

Katalogaufnahmen nach JahrEach 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.
Katalogaufnahmen nach Jahr · dateAdded
AufnahmejahrEinträge
2021311
2022555
2023187
2024186
2025245
2026285

Ergebnisse : 1769 / 1769 · Seite 43 / 71

CISA-KEV-Katalog durchsuchen · 2026.11.06
CVEAnbieter oder Projekt · productAufnahmedatum / Frist des EintragsNutzung in Ransomware-Kampagnen / forensicTriage
CVE-2015-0016

CWE-22

Microsoft

Windows

Von CISA veröffentlichter Eintrag und Maßnahme

Microsoft Windows TS WebProxy Directory Traversal Vulnerability

Directory traversal vulnerability in the TS WebProxy (TSWbPrxy) component in Microsoft Windows allows remote attackers to escalate privileges.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2015-0016

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2015-0071

CWE-264

Microsoft

Internet Explorer

Von CISA veröffentlichter Eintrag und Maßnahme

Microsoft Internet Explorer ASLR Bypass Vulnerability

Microsoft Internet Explorer allows remote attackers to bypass the address space layout randomization (ASLR) protection mechanism via a crafted web site.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2015-0071

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2015-0310

CWE-264

Adobe

Flash Player

Von CISA veröffentlichter Eintrag und Maßnahme

Adobe Flash Player ASLR Bypass Vulnerability

Adobe Flash Player does not properly restrict discovery of memory addresses, which allows attackers to bypass the address space layout randomization (ASLR) protection mechanism.

requiredAction
The impacted product is end-of-life and should be disconnected if still in use.
notes
https://nvd.nist.gov/vuln/detail/CVE-2015-0310

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2015-1671

CWE-19

Microsoft

Windows

Von CISA veröffentlichter Eintrag und Maßnahme

Microsoft Windows Remote Code Execution Vulnerability

A remote code execution vulnerability exists when components of Windows, .NET Framework, Office, Lync, and Silverlight fail to properly handle TrueType fonts.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2015-1671

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2015-1769

CWE-264

Microsoft

Windows

Von CISA veröffentlichter Eintrag und Maßnahme

Microsoft Windows Mount Manager Privilege Escalation Vulnerability

A privilege escalation vulnerability exists when the Windows Mount Manager component improperly processes symbolic links.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2015-1769

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2015-2360

CWE-119

Microsoft

Win32k

Von CISA veröffentlichter Eintrag und Maßnahme

Microsoft Win32k Privilege Escalation Vulnerability

Win32k.sys in the kernel-mode drivers in Microsoft Windows allows local users to gain privileges or cause denial-of-service (DoS).

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2015-2360

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2015-2425

CWE-119

Microsoft

Internet Explorer

Von CISA veröffentlichter Eintrag und Maßnahme

Microsoft Internet Explorer Memory Corruption Vulnerability

Microsoft Internet Explorer contains a memory corruption vulnerability that allows remote attackers to execute code or cause denial-of-service (DoS).

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2015-2425

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2015-4495

CWE-200

Mozilla

Firefox

Von CISA veröffentlichter Eintrag und Maßnahme

Mozilla Firefox Security Feature Bypass Vulnerability

Moxilla Firefox allows remote attackers to bypass the Same Origin Policy to read arbitrary files or gain privileges.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2015-4495

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2015-6175

CWE-264

Microsoft

Windows

Von CISA veröffentlichter Eintrag und Maßnahme

Microsoft Windows Kernel Privilege Escalation Vulnerability

The kernel in Microsoft Windows contains a vulnerability that allows local users to gain privileges via a crafted application.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2015-6175

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2015-8651

CWE-189

Adobe

Flash Player

Von CISA veröffentlichter Eintrag und Maßnahme

Adobe Flash Player Integer Overflow Vulnerability

Integer overflow in Adobe Flash Player allows attackers to execute code.

requiredAction
The impacted product is end-of-life and should be disconnected if still in use.
notes
https://nvd.nist.gov/vuln/detail/CVE-2015-8651

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2016-0034

CWE-20

Microsoft

Silverlight

Von CISA veröffentlichter Eintrag und Maßnahme

Microsoft Silverlight Runtime Remote Code Execution Vulnerability

Microsoft Silverlight mishandles negative offsets during decoding, which allows attackers to execute remote code or cause a denial-of-service (DoS).

requiredAction
The impacted products are end-of-life and should be disconnected if still in use.
notes
https://nvd.nist.gov/vuln/detail/CVE-2016-0034

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Known
forensicTriage
No
CVE-2016-0984

CWE-416

Adobe

Flash Player and AIR

Von CISA veröffentlichter Eintrag und Maßnahme

Adobe Flash Player and AIR Use-After-Free Vulnerability

Use-after-free vulnerability in Adobe Flash Player and Adobe AIR allows attackers to execute code.

requiredAction
The impacted products are end-of-life and should be disconnected if still in use.
notes
https://nvd.nist.gov/vuln/detail/CVE-2016-0984

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2016-1010

CWE-190

Adobe

Flash Player and AIR

Von CISA veröffentlichter Eintrag und Maßnahme

Adobe Flash Player and AIR Integer Overflow Vulnerability

Integer overflow vulnerability in Adobe Flash Player and AIR allows attackers to execute code.

requiredAction
The impacted products are end-of-life and should be disconnected if still in use.
notes
https://nvd.nist.gov/vuln/detail/CVE-2016-1010

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2016-3393

CWE-284

Microsoft

Windows

Von CISA veröffentlichter Eintrag und Maßnahme

Microsoft Windows Graphics Device Interface (GDI) Remote Code Execution Vulnerability

A remote code execution vulnerability exists due to the way the Windows GDI component handles objects in the memory. An attacker who successfully exploits this vulnerability could take control of the affected system.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2016-3393

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2016-7256

CWE-284

Microsoft

Windows

Von CISA veröffentlichter Eintrag und Maßnahme

Microsoft Windows Open Type Font Remote Code Execution Vulnerability

A remote code execution vulnerability exists when the Windows font library improperly handles specially crafted embedded fonts. An attacker who successfully exploits this vulnerability could take control of the affected system.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2016-7256

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2019-3010

Oracle

Solaris

Von CISA veröffentlichter Eintrag und Maßnahme

Oracle Solaris Privilege Escalation Vulnerability

Oracle Solaris component: XScreenSaver contains an unspecified vulnerability that allows for privilege escalation.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2019-3010

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2016-0162

CWE-200

Microsoft

Internet Explorer

Von CISA veröffentlichter Eintrag und Maßnahme

Microsoft Internet Explorer Information Disclosure Vulnerability

An information disclosure vulnerability exists when Internet Explorer does not properly handle JavaScript. The vulnerability could allow an attacker to detect specific files on the user's computer.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2016-0162

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2016-3298

CWE-200

Microsoft

Internet Explorer

Von CISA veröffentlichter Eintrag und Maßnahme

Microsoft Internet Explorer Messaging API Information Disclosure Vulnerability

An information disclosure vulnerability exists when the Microsoft Internet Messaging API improperly handles objects in memory. An attacker who successfully exploited this vulnerability could allow the attacker to test for the presence of files on disk.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2016-3298

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2016-3351

CWE-200

Microsoft

Internet Explorer and Edge

Von CISA veröffentlichter Eintrag und Maßnahme

Microsoft Internet Explorer and Edge Information Disclosure Vulnerability

An information disclosure vulnerability exists in the way that certain functions in Internet Explorer and Edge handle objects in memory. The vulnerability could allow an attacker to detect specific files on the user's computer.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2016-3351

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Known
forensicTriage
No
CVE-2016-4655

CWE-200

Apple

iOS

Von CISA veröffentlichter Eintrag und Maßnahme

Apple iOS Information Disclosure Vulnerability

The Apple iOS kernel allows attackers to obtain sensitive information from memory via a crafted application.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2016-4655

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2016-4656

CWE-264

Apple

iOS

Von CISA veröffentlichter Eintrag und Maßnahme

Apple iOS Memory Corruption Vulnerability

A memory corruption vulnerability in Apple iOS kernel allows attackers to execute code in a privileged context or cause a denial-of-service (DoS) via a crafted application.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2016-4656

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2016-4657

CWE-119

Apple

iOS

Von CISA veröffentlichter Eintrag und Maßnahme

Apple iOS Webkit Memory Corruption Vulnerability

Apple iOS WebKit contains a memory corruption vulnerability that allows attackers to execute remote code or cause a denial-of-service (DoS) via a crafted web site. This vulnerability could impact HTML parsers that use WebKit, including but not limited to Apple Safari and non-Apple products which rely on WebKit for HTML processing.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2016-4657

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2016-6366

CWE-119

Cisco

Adaptive Security Appliance (ASA)

Von CISA veröffentlichter Eintrag und Maßnahme

Cisco Adaptive Security Appliance (ASA) SNMP Buffer Overflow Vulnerability

A buffer overflow vulnerability in the Simple Network Management Protocol (SNMP) code of Cisco ASA software could allow an attacker to cause a reload of the affected system or to remotely execute code.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2016-6366

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2016-6367

CWE-77

Cisco

Adaptive Security Appliance (ASA)

Von CISA veröffentlichter Eintrag und Maßnahme

Cisco Adaptive Security Appliance (ASA) CLI Remote Code Execution Vulnerability

A vulnerability in the command-line interface (CLI) parser of Cisco ASA software could allow an authenticated, local attacker to create a denial-of-service (DoS) condition or potentially execute code.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2016-6367

nvd.nist.gov ↗

dateAdded
dueDate
knownRansomwareCampaignUse
Unknown
forensicTriage
No
CVE-2017-0005

CWE-119

Microsoft

Windows

Von CISA veröffentlichter Eintrag und Maßnahme

Microsoft Windows Graphics Device Interface (GDI) Privilege Escalation Vulnerability

The Graphics Device Interface (GDI) in Microsoft Windows allows local users to gain privileges via a crafted application.

requiredAction
Apply updates per vendor instructions.
notes
https://nvd.nist.gov/vuln/detail/CVE-2017-0005

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.

Quelleninformationen · CISA KEV

How we publish this official snapshot

Ausführliche Hinweise stehen in dieser Ausgabe auf Englisch zur Verfügung.

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.

Katalog und Methode ansehen →

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.

Offizielle Referenzen

Die Referenzen unterstützen die Methode. Passen Sie die Prüfungen an Ihren Kontext an; sie stellen keine Zertifizierung dar. Originalreferenztitel und Quelldokumente können in einer anderen Sprache verfasst sein.

Referenzen geprüft am .