GHSA-8gmx-w9m8-vx7q: openssl-encrypt (CVE-2026-81706)

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

CVSS 9.3 CriticalCriticalEPSS 0.0018 · 7th percentile

Critical, because:

CVSS score 9.3: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 27 Aug 2026, 17:21 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

Package	Ecosystem	Affected	Fixed in
openssl-encrypt	PyPI	<1.4.9	1.4.9

Identifiers

GHSA-8gmx-w9m8-vx7q · CVE-2026-81706 · PYSEC-2026-3781

Weakness (CWE)

CWE-345

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions of openssl-encrypt before 1.4.9 do not prevent name collisions between a user's own identities and contacts in IdentityStore. An attacker can create a contact that is hidden behind an own identity with the same name, and when that own identity is deleted, the hidden contact becomes visible and resolves to the attacker's keys, allowing silent key substitution for encrypted files. The source does not state what access the attacker needs. Upgrade to openssl-encrypt 1.4.9.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

Score	Rating	CVSS	Vector	Source
9.3	Critical	4.0	CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N	CNA (VulnCheck)

CISA KEV Not listed.
EPSS 0.0018, the 7th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

31 Oct 2026, 14:38 UTC First seen by agentprime
31 Oct 2026, 14:38 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.