CVE-2026-74882openssl_encrypt before 1.4.0 Insecure Default Configuration
Updated under an hour ago ()
Does this affect you?
It affects jahlives openssl_encrypt. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 7.5 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Weakness (CWE)
- CWE-345
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- VulnCheck
- NVD analysis
- Analyzed
- Record last updated
- Oct 1, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
jahlives openssl_encrypt jahlives:openssl_encrypt (from the name) | before 1.4.0; 1.4.0 not affected | CNA record |
jahlives openssl_encrypt jahlives:openssl_encrypt | before 1.4.0 | NVD |
References
- https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-2592-7m3g-7fq6vendor-advisory, mitigation
- https://www.vulncheck.com/advisories/openssl-encrypt-before-insecure-default-configurationthird-party-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.