Vulnerability · Published Aug 17, 2026 · Assigned by VulnCheck

CVE-2026-74882openssl_encrypt before 1.4.0 Insecure Default Configuration

High 7.5

In plain English

A high-severity insufficient verification of data authenticity in openssl_encrypt from jahlives. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 6% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.5High

Exploit odds (30 days)0.2%top 94.0% of all CVEs

Exploited in the wildNo reportsCISA SSVC: none

Attack toolingNoneno public tooling known

Official description

openssl_encrypt versions before 1.4.0 contain an insecure default configuration that trusts the entire RFC 1918 private address space in IntegrityProxyConfig trusted_proxies. Attackers on private networks can forge client certificate headers to bypass mTLS authentication when ProxyAuth validation is relaxed or modified.

Affected packages & fixed versions

Ecosystem	Package	Fixed in	Advisory
PyPI	openssl-encrypt	1.4.0	PYSEC-2026-3744

Affected products (as reported)

Vendor	Product	Versions
jahlives	openssl_encrypt	0 – before 1.4.0

Weakness: CWE-345 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

References

GitHub Security Advisory (GHSA-2592-7m3g-7fq6) vendor-advisory
VulnCheck Advisory: openssl_encrypt before 1.4.0 Insecure Default Configuration third-party-advisory