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 prior to version 1.4.0 involves insufficient verification of data authenticity due to a default configuration that implicitly trusts all RFC 1918 private IP addresses as trusted proxies. This configuration flaw enables an attacker within a private network to forge client certificate headers, effectively bypassing mTLS authentication mechanisms if ProxyAuth validation is not strictly enforced. The vulnerability has a CVSS 4.0 base score of 8.7, indicating high severity, with network attack vector, low attack complexity, and no required privileges or user interaction. There is no official remediation or patch currently documented.
Potential Impact
An attacker on a private network can exploit this vulnerability to bypass mTLS authentication by forging client certificate headers, potentially gaining unauthorized access to systems relying on this authentication method. This undermines the integrity of authentication and could lead to unauthorized access or impersonation within affected environments.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, administrators should avoid relaxing or modifying ProxyAuth validation and should not rely on the default trusted_proxies configuration that trusts the entire RFC 1918 private address space. Implement strict validation of client certificates and proxy authentication settings to mitigate the risk.
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
jahlives
openssl_encrypt
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 prior to version 1.4.0 involves insufficient verification of data authenticity due to a default configuration that implicitly trusts all RFC 1918 private IP addresses as trusted proxies. This configuration flaw enables an attacker within a private network to forge client certificate headers, effectively bypassing mTLS authentication mechanisms if ProxyAuth validation is not strictly enforced. The vulnerability has a CVSS 4.0 base score of 8.7, indicating high severity, with network attack vector, low attack complexity, and no required privileges or user interaction. There is no official remediation or patch currently documented.
Potential Impact
An attacker on a private network can exploit this vulnerability to bypass mTLS authentication by forging client certificate headers, potentially gaining unauthorized access to systems relying on this authentication method. This undermines the integrity of authentication and could lead to unauthorized access or impersonation within affected environments.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, administrators should avoid relaxing or modifying ProxyAuth validation and should not rely on the default trusted_proxies configuration that trusts the entire RFC 1918 private address space. Implement strict validation of client certificates and proxy authentication settings to mitigate the risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-17T10:36:18.506Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a82f004bf8831d539c4834e
Added to database: 08/17/2026, 11:27:00 UTC
Last enriched: 08/24/2026, 13:10:14 UTC
Last updated: 10/01/2026, 15:31:50 UTC
Views: 68
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.