Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-2592-7m3g-7fq6

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 n...

CVSS 8.7 HighEPSS 0.0017 · 5th percentile

Published by the GitHub Advisory Database at 17 Aug 2026, 11:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
openssl-encryptPyPI<1.4.01.4.0
Identifiers
GHSA-2592-7m3g-7fq6 · CVE-2026-74882 · PYSEC-2026-3744
Weakness (CWE)
CWE-345
Tags
Published
17 Aug 2026
Updated
1 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

openssl-encrypt versions before 1.4.0 ship a default IntegrityProxyConfig trusted_proxies setting that trusts the entire RFC 1918 private address space. An attacker on a private network can forge client certificate headers to bypass mTLS authentication, but only when ProxyAuth validation has been relaxed or modified. Upgrade to openssl-encrypt 1.4.0 or later, which fixes the issue. The source gives few details on the exact conditions required.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.7 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0017, the 5th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:39 UTC First seen by agentprime
  2. 31 Oct 2026, 14:39 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.