Exploitation riskProbably exploitedHow this is measuredCombines four public sources, each answering a different question. CVSS (NVD) scores how bad exploitation would be. KEV (CISA) confirms exploitation is happening. EPSS (FIRST) estimates the chance of exploitation in the next 30 days. LEV (NIST CSWP 41) compounds a CVE's own EPSS history into the chance it has already been exploited. “Elevated” means EPSS at or above 10%; LEV is counted as material at 10%. LEV and EPSS are statistical estimates about a vulnerability, not findings about this vendor — and LEV is a stated lower bound, so “10%” means “at least 10%”, never “probably happened”. The underlying CVEs are matched to this vendor by name, not by exact product/version, so check each linked NVD record before drawing conclusions.
4 of 4 CVEs assessed
0
confirmed exploited
0
EPSS ≥ 10%
>99%
highest single CVE
1 CVE has an estimated 10%-or-higher chance of having already been exploited despite not appearing on CISA's KEV catalog. KEV is a curated record of confirmed cases rather than a complete census, so this is where its coverage is likely thinnest — an estimate from EPSS history, not a finding. Based on a median of 2 EPSS observations per CVE.
Likely-exploited estimates here rest on a median of 2 EPSS observations per CVE — too little history to read as a trend yet. It deepens daily as scores are collected.
Stack-based buffer overflow in kkstrtext.h in ktools library 0.3 and earlier, as used in products such as (1) centericq, (2) orpheus, (3) motor, and (4) groan, …
Heimdal before 7.4 allows remote attackers to impersonate services with Orpheus' Lyre attacks because it obtains service-principal names in a way that violates …
Microsoft Windows 7 SP1, Windows Server 2008 SP2 and R2 SP1, Windows 8.1 and Windows RT 8.1, Windows Server 2012 and R2, Windows 10 Gold, 1511, 1607, and 1703, …
Recent changes
last 90 days
CVE-2005-3863 is now estimated at a 100% chance of having already been exploited, despite not appearing on CISA's Known Exploited Vulnerabilities catalog.2026-09-01 · NVD ↗
CVE-2017-11103 is now estimated at a 100% chance of having already been exploited, despite not appearing on CISA's Known Exploited Vulnerabilities catalog.2026-09-01 · NVD ↗
CVE-2017-8495 is now estimated at a 99% chance of having already been exploited, despite not appearing on CISA's Known Exploited Vulnerabilities catalog.2026-08-31 · NVD ↗
CVE-2005-3863 is now estimated at a 100% chance of having already been exploited, despite not appearing on CISA's Known Exploited Vulnerabilities catalog.2026-08-31 · NVD ↗
CVE-2017-11103 is now estimated at a 100% chance of having already been exploited, despite not appearing on CISA's Known Exploited Vulnerabilities catalog.2026-08-31 · NVD ↗
CVE severity over timeUI-24 — CVE severity timelineEvery known CVE with a disclosure date and severity, plotted by when it was published — lets you see whether disclosures are trending toward more or less severe, not just a raw count. Same NVD-sourced, name-matched data as the list below.
CVEs by year and severity
Count of matched CVEs by the year NVD published them.
Year
Critical
High
Medium
Low
Unscored
Total
2026
0
1
0
0
0
1
2017
0
2
0
0
0
2
2005
0
1
0
0
0
1
Highest EPSS scores
EPSS is FIRST's estimate of the chance a CVE is exploited in the next 30 days. It measures likelihood, not impact.
Known CVEs (4)About this listSourced from the public NVD database, matched by vendor name. This is a name-based match, not exact version tracking — always check the linked NVD record for affected versions before drawing conclusions. “New” means published within the last 30 days. “Actively exploited” means CISA's Known Exploited Vulnerabilities (KEV) catalog confirms real-world exploitation, not just a theoretical severity score. An “EPSS” chip appears at 10% and above: that is FIRST's estimated chance of exploitation in the next 30 days, which measures likelihood rather than impact and so can differ sharply from the severity beside it. See the Exploitation risk panel above for the full picture.
Heimdal before 7.4 allows remote attackers to impersonate services with Orpheus' Lyre attacks because it obtains service-principal names in a way that violates the Kerberos 5 protocol specification. I…
CVEs come from the US National Vulnerability Database (NVD) and are matched to Orpheus by vendor name. A name match can include CVEs that concern a similarly named product, and can miss ones filed under another name. The count reflects how widely a vendor's software is deployed and examined as much as anything else, so it is not a measure of how secure the vendor is and should not be used to rank vendors. Latest CVE added here: 2026-07-11.
Known-exploited status comes from the CISA Known Exploited Vulnerabilities (KEV) catalog. Last checked: 2026-10-20.
Exploit probability (EPSS) comes from FIRST. Latest score date: 2026-10-20.
Unauthenticated Local File Inclusion in Orpheus <= 1.3 versions.
CVE-2005-3863 received its first EPSS score: 5.2% chance of exploitation in the next 30 days.2026-08-31 · NVD ↗
CVE-2017-11103 received its first EPSS score: 5.1% chance of exploitation in the next 30 days.2026-08-31 · NVD ↗
2017
Microsoft Windows 7 SP1, Windows Server 2008 SP2 and R2 SP1, Windows 8.1 and Windows RT 8.1, Windows Server 2012 and R2, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 allows an attack…
Stack-based buffer overflow in kkstrtext.h in ktools library 0.3 and earlier, as used in products such as (1) centericq, (2) orpheus, (3) motor, and (4) groan, allows local users or remote attackers t…
