CVE
CVE-2026-12577
DVP80ES3 with Improperly Implemented Security Check for Standard vulnerability.
DVP80ES3 with Improperly Implemented Security Check for Standard vulnerability.
EPSS 0.00253
EPSS exploitation odds0.25% · top 83%
Schedule remediation
- SSVC automatable: yes - attacks can be scripted at scale
- ⚠ NVD has not scored this CVE yet - manual triage required (common for recent CVEs)
Sigma rules0
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2026-12577, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
▣
Severity & exploitation scoring
EPSS exploitation probability
0.25%
Top 83%odds of exploitation in the next 30 days
CVSS metric silhouette
No structured CVSS vector for this CVE. Older entries often have only a numeric base score - the metric breakdown radar requires a full
AV:_/AC:_/... vector string published by NVD.SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
yes
Tech impact
partial
⬡
Weakness Classification
▤
Related CVEs
4CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row.
CVE-2014-4843
Curam Universal Access in IBM Curam Social Program Management (SPM) 6.0 SP2 befo...
same CWE-358
MEDIUM
CVE-2016-3017
IBM Security Access Manager for Web could allow a remote attacker to obtain sens...
same CWE-358
HIGH
CVE-2016-10229
udp.c in the Linux kernel before 4.5 allows remote attackers to execute arbitrar...
same CWE-358
CRITICAL
CVE-2016-8614
A flaw was found in Ansible before version 2.2.0. The apt_key module does not pr...
same CWE-358
MEDIUM
🔗
References & Sources
1Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.