CVE-2026-81706

MEDIUMNVD 6.86.8—
EchelonGraph scoreHIGH confidence

Score 6.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-27. NVD baseline CVSS 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

openssl_encrypt before 1.4.9 fails to prevent namespace collisions between own identities and contacts in IdentityStore, allowing attackers to create shadowed contact entries invisible until the corresponding own identity is deleted. When the own identity is deleted, the shadowed contact becomes visible and resolves to the attacker's keys, enabling silent key substitution for encrypted files.

CVSS v3
6.8
EG Score
6.8(high)
EG Risk
31(Track)
EG Risk 31/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity68% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 27, 2026

Last Modified

September 1, 2026

Advisory Details (2)

Auto-updated Aug 27, 2026
Patch available. Sources: github.
generic

openssl_encrypt before 1.4.9 Key Substitution via Identity Shadowing | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openssl-encrypt-before-1.4.9-key-substitution-via-identity-shadowing
github Patch Available

Contact stored under an own identity's name silently substitutes its keys when the identity is deleted · Advisory · jahlives/openssl_encrypt · GitHub

https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-8gmx-w9m8-vx7q

Vendor Advisories for CVE-2026-81706(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
openssl-encrypt0.2.2 ... 1.4.8 (53 versions)1.4.9—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 60× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 02:41 UTCEG score recompute
  2. 2026-09-19 02:41 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 00:47 UTCEG score recompute
  5. 2026-09-18 00:47 UTCGHSA enrichment
  6. 2026-09-16 22:53 UTCEG score recompute
  7. 2026-09-16 22:53 UTCGHSA enrichment
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-15 20:57 UTCEG score recompute
  10. 2026-09-15 20:57 UTCGHSA enrichment
  11. 2026-09-15 03:12 UTCEPSS rescore
  12. 2026-09-15 03:12 UTCEPSS rescore
  13. 2026-09-14 18:48 UTCEG score recompute
  14. 2026-09-14 18:48 UTCGHSA enrichment
  15. 2026-09-13 15:38 UTCEG score recompute
  16. 2026-09-13 15:38 UTCGHSA enrichment
  17. 2026-09-12 13:45 UTCGHSA enrichment
  18. 2026-09-11 11:51 UTCEG score recompute
  19. 2026-09-11 11:51 UTCGHSA enrichment
  20. 2026-09-10 09:47 UTCEG score recompute
  21. 2026-09-10 09:47 UTCGHSA enrichment
  22. 2026-09-09 07:53 UTCEG score recompute
  23. 2026-09-09 07:53 UTCGHSA enrichment
  24. 2026-09-08 22:01 UTCEPSS rescore
  25. 2026-09-08 06:00 UTCEG score recompute
Show 35 more
  1. 2026-09-08 06:00 UTCGHSA enrichment
  2. 2026-09-07 04:05 UTCEG score recompute
  3. 2026-09-07 04:05 UTCGHSA enrichment
  4. 2026-09-06 13:48 UTCEPSS rescore
  5. 2026-09-06 02:11 UTCEG score recompute
  6. 2026-09-06 02:11 UTCGHSA enrichment
  7. 2026-09-05 15:31 UTCEPSS rescore
  8. 2026-09-05 00:18 UTCEG score recompute
  9. 2026-09-05 00:18 UTCGHSA enrichment
  10. 2026-09-03 22:23 UTCGHSA enrichment
  11. 2026-09-02 20:29 UTCEG score recompute
  12. 2026-09-02 20:29 UTCGHSA enrichment
  13. 2026-09-02 14:12 UTCEPSS rescore
  14. 2026-09-01 18:04 UTCEG score recompute
  15. 2026-09-01 18:04 UTCGHSA enrichment
  16. 2026-09-01 13:54 UTCEPSS rescore
  17. 2026-09-01 04:40 UTCEPSS rescore
  18. 2026-09-01 04:40 UTCEPSS rescore
  19. 2026-09-01 00:44 UTCGHSA enrichment
  20. 2026-08-30 22:50 UTCEG score recompute
  21. 2026-08-30 22:50 UTCGHSA enrichment
  22. 2026-08-30 19:18 UTCEPSS rescore
  23. 2026-08-30 19:17 UTCEPSS rescore
  24. 2026-08-30 01:22 UTCEPSS rescore
  25. 2026-08-29 20:57 UTCEG score recompute
  26. 2026-08-29 20:57 UTCGHSA enrichment
  27. 2026-08-28 21:42 UTCEPSS rescore
  28. 2026-08-28 19:03 UTCGHSA enrichment
  29. 2026-08-27 20:27 UTCEG score recompute
  30. 2026-08-27 20:27 UTCGHSA enrichment
  31. 2026-08-27 20:17 UTCEG score recompute
  32. 2026-08-27 20:17 UTCGHSA enrichment
  33. 2026-08-27 17:25 UTCEG score recompute
  34. 2026-08-27 16:47 UTCEG score recompute
  35. 2026-08-27 16:43 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-81706?
CVE-2026-81706 is a medium vulnerability published on August 27, 2026. openssl_encrypt before 1.4.9 fails to prevent namespace collisions between own identities and contacts in IdentityStore, allowing attackers to create shadowed contact entries invisible until the corresponding own identity is deleted. When the own identity is deleted, the shadowed contact becomes…
When was CVE-2026-81706 disclosed?
CVE-2026-81706 was first published in the National Vulnerability Database on August 27, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81706 actively exploited?
CVE-2026-81706 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.9% of all scored CVEs.
What is the CVSS score of CVE-2026-81706?
CVE-2026-81706 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-81706?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81706, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-81706

Explore →

Is Your Infrastructure Affected by CVE-2026-81706?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs