CVE-2026-74882: Insufficient Verification of Data Authenticity in jahlives openssl_encrypt
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.
AI Analysis
Technical Summary
The vulnerability in jahlives openssl_encrypt versions before 1.4.0 stems from an insecure default configuration that implicitly trusts all private IP addresses defined by RFC 1918 within the IntegrityProxyConfig trusted_proxies. This trust model enables attackers located on private networks to forge client certificate headers. When ProxyAuth validation is relaxed or altered, these forged headers can bypass mTLS authentication, potentially allowing unauthorized access. The CVSS 4.0 base score is 8.7, indicating a high impact with network attack vector, low complexity, and no required privileges or user interaction. No official patch or remediation guidance is currently provided by the vendor, and no known exploits are reported in the wild.
Potential Impact
Attackers on private networks can exploit this vulnerability to bypass mTLS authentication by forging client certificate headers, potentially gaining unauthorized access to systems relying on openssl_encrypt's IntegrityProxyConfig trusted_proxies. This undermines the integrity of authentication mechanisms in affected deployments.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, administrators should avoid relaxing or modifying ProxyAuth validation and restrict trusted proxies configurations to minimize exposure to private network attackers.
CVE-2026-74882: Insufficient Verification of Data Authenticity in jahlives openssl_encrypt
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.
CVSS v4.0
Score 8.7high
Affected software
pkg:github/jahlives/openssl_encryptRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in jahlives openssl_encrypt versions before 1.4.0 stems from an insecure default configuration that implicitly trusts all private IP addresses defined by RFC 1918 within the IntegrityProxyConfig trusted_proxies. This trust model enables attackers located on private networks to forge client certificate headers. When ProxyAuth validation is relaxed or altered, these forged headers can bypass mTLS authentication, potentially allowing unauthorized access. The CVSS 4.0 base score is 8.7, indicating a high impact with network attack vector, low complexity, and no required privileges or user interaction. No official patch or remediation guidance is currently provided by the vendor, and no known exploits are reported in the wild.
Potential Impact
Attackers on private networks can exploit this vulnerability to bypass mTLS authentication by forging client certificate headers, potentially gaining unauthorized access to systems relying on openssl_encrypt's IntegrityProxyConfig trusted_proxies. This undermines the integrity of authentication mechanisms in affected deployments.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, administrators should avoid relaxing or modifying ProxyAuth validation and restrict trusted proxies configurations to minimize exposure to private network attackers.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-17T10:36:18.506Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a82f004bf8831d539c4834e
Added to database: 08/17/2026, 11:27:00 UTC
Last enriched: 08/17/2026, 11:43:02 UTC
Last updated: 08/17/2026, 13:16:32 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.