CVE-2026-74882 openssl_encrypt before 1.4.0 Insecure Default Configuration

High 8.7 Published Updated

Attackers on private networks can forge client certificate headers to bypass mTLS authentication due to insecure default proxy trust settings.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-74882?

CVE-2026-74882 is a high-severity authentication bypass vulnerability in Jahlives Openssl Encrypt, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

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.

Weakness: CWE-345

Which versions are affected by CVE-2026-74882?

1 open source package ship an affected version, including openssl-encrypt. It affects 1 product.

PackageAffectedFixed in
openssl-encrypt PyPIAll versions1.4.0

Products include Jahlives Openssl Encrypt.

How do I fix CVE-2026-74882?

Upgrade openssl-encrypt to 1.4.0 or later.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is CVE-2026-74882 being exploited?

There is no known exploitation of CVE-2026-74882 in the wild and no public exploit code.

All Jahlives Openssl Encrypt vulnerabilities

Sources

Also known as GHSA-24vg-mjm2-36jv, GHSA-2592-7m3g-7fq6, PYSEC-2026-3744.

Is CVE-2026-74882 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free