CVE-2025-9232: Out-of-bounds read in HTTP client no_proxy handling
Noroxi assessment
Priority: Monitor (action score 24/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.4% (FIRST EPSS); higher than 84.3% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: OpenSSL OpenSSL 3.0.18, 3.2.6, 3.3.5; azl3 openssl 3.3.3-3 on Azure Linux 3.0 3.3.5-1.
Low priority for now. Upgrade to OpenSSL OpenSSL 3.0.18, 3.2.6, 3.3.5; azl3 openssl 3.3.3-3 on Azure Linux 3.0 3.3.5-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Issue summary: An application using the OpenSSL HTTP client API functions may trigger an out-of-bounds read if the 'no_proxy' environment variable is set and the host portion of the authority component of the HTTP URL is an IPv6 address. Impact summary: An out-of-bounds read can trigger a crash which leads to Denial of Service for an application. The OpenSSL HTTP client API functions can be used directly by applications but they are also used by the OCSP client functions and CMP (Certificate Management Protocol) client implementation in OpenSSL. However the URLs used by these implementations are unlikely to be controlled by an attacker. In this vulnerable code the out of bounds read can only trigger a crash. Furthermore the vulnerability requires an attacker-controlled URL to be passed from an application to the OpenSSL function and the user has to have a 'no_proxy' environment variable set. For the aforementioned reasons the issue was assessed as Low severity. The vulnerable code was introduced in the following patch releases: 3.0.16, 3.1.8, 3.2.4, 3.3.3, 3.4.0 and 3.5.0. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the HTTP client implementation is outside the OpenSSL FIPS module boundary.
- Published
- Sep 30, 2025
- Updated
- Nov 9, 2026
- EPSS
- 2.4% · 84th percentile
- CWE
- CWE-125
Report tools
Action score
24
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Check your server's TLS configurationRun the SSL check
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| openssl | openssl | cpe:2.3:a:openssl:openssl |
| siemens | simatic cn 4100 firmware | cpe:2.3:o:siemens:simatic_cn_4100_firmware |
| siemens | simatic cn 4100 | cpe:2.3:h:siemens:simatic_cn_4100 |
| siemens | simatic s7-1500 cpu 1518-4 pn/dp mfp firmware | cpe:2.3:o:siemens:simatic_s7-1500_cpu_1518-4_pn/dp_mfp_firmware |
| siemens | simatic s7-1500 cpu 1518-4 pn/dp mfp | cpe:2.3:h:siemens:simatic_s7-1500_cpu_1518-4_pn/dp_mfp |
| siemens | simatic s7-1500 cpu 1518f-4 pn/dp mfp firmware | cpe:2.3:o:siemens:simatic_s7-1500_cpu_1518f-4_pn/dp_mfp_firmware |
| siemens | simatic s7-1500 cpu 1518f-4 pn/dp mfp | cpe:2.3:h:siemens:simatic_s7-1500_cpu_1518f-4_pn/dp_mfp |
| siemens | siplus s7-1500 cpu 1518-4 pn/dp mfp firmware | cpe:2.3:o:siemens:siplus_s7-1500_cpu_1518-4_pn/dp_mfp_firmware |
| siemens | siplus s7-1500 cpu 1518-4 pn/dp mfp | cpe:2.3:h:siemens:siplus_s7-1500_cpu_1518-4_pn/dp_mfp |
| siemens | sinec os | cpe:2.3:o:siemens:sinec_os |
| siemens | scalance xc316-8 | cpe:2.3:h:siemens:scalance_xc316-8 |
| siemens | scalance xc319-4 | cpe:2.3:h:siemens:scalance_xc319-4 |
and 30 more
Check your server's TLS configuration
The OpenSSL version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.
Run the SSL checkVersions reported by the vendor
Affected version ranges reported by the assigning authority (openssl). Independent of NVD's CPE analysis and usually ahead of it.
OpenSSL OpenSSL
- 3.5.0 and later · before 3.5.4affected · semver
- 3.4.0 and later · before 3.4.3affected · semver
- 3.3.3 and later · before 3.3.5affected · semver
- 3.2.4 and later · before 3.2.6affected · semver
- 3.0.16 and later · before 3.0.18affected · semver
Affected versions · NVD (15)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- openssl openssl1.0.2 and later · before 1.0.2zm
- openssl openssl1.1.1 and later · before 1.1.1zd
- openssl openssl3.0.0 and later · before 3.0.18
- openssl openssl3.2.0 and later · before 3.2.6
- openssl openssl3.3.0 and later · before 3.3.5
- openssl openssl3.4.0 and later · before 3.4.3
- openssl openssl3.5.0 and later · before 3.5.4
- siemens ruggedcom rst2428p firmwarebefore 4.0
- siemens sidis primebefore 4.0.800
- siemens sidis secured smartplug firmwarebefore 7.26.0310
- siemens simatic cn 4100 firmwarebefore 5.0
- siemens simatic s7-1500 cpu 1518-4 pn/dp mfp firmware3.1.5
- siemens simatic s7-1500 cpu 1518f-4 pn/dp mfp firmware3.1.5
- siemens sinec osbefore 3.3
- siemens siplus s7-1500 cpu 1518-4 pn/dp mfp firmware3.1.5
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.17 | openssl | from 1.0.2 · before 3.0.19-r0 | 3.0.19-r0 |
| Alpine:v3.19 | openssl | from 1.0.2 · before 3.1.8-r1 | 3.1.8-r1 |
| Alpine:v3.20 | openssl | from 1.0.2 · before 3.3.5-r0 | 3.3.5-r0 |
| Alpine:v3.22 | openssl | from 1.0.2 · before 3.5.4-r0 | 3.5.4-r0 |
| Debian:12 | openssl | before 3.0.17-1~deb12u3 | 3.0.17-1~deb12u3 |
| Debian:13 | openssl | before 3.5.1-1+deb13u1 | 3.5.1-1+deb13u1 |
| Debian:14 | openssl | before 3.5.4-1 | 3.5.4-1 |
| openSUSE:Leap 16.0 | openssl-3 | before 3.5.0-160000.4.1 | 3.5.0-160000.4.1 |
| openSUSE:Tumbleweed | openssl-3 | before 3.5.3-2.1 | 3.5.3-2.1 |
| openSUSE:Tumbleweed | regclient | before 0.10.0-1.1 | 0.10.0-1.1 |
| Red Hat:hummingbird:1 | openssl | before 0:3.5.6-0.1.hum1 | 0:3.5.6-0.1.hum1 |
| Red Hat:hummingbird:1 | openssl-config-fips | before 0:3.5.6-0.1.hum1 | 0:3.5.6-0.1.hum1 |
| Red Hat:hummingbird:1 | openssl-devel | before 0:3.5.6-0.1.hum1 | 0:3.5.6-0.1.hum1 |
| Red Hat:hummingbird:1 | openssl-devel-engine | before 0:3.5.6-0.1.hum1 | 0:3.5.6-0.1.hum1 |
| Red Hat:hummingbird:1 | openssl-libs | before 0:3.5.6-0.1.hum1 | 0:3.5.6-0.1.hum1 |
| Red Hat:hummingbird:1 | openssl-perl | before 0:3.5.6-0.1.hum1 | 0:3.5.6-0.1.hum1 |
| SUSE:Linux Enterprise Server 16.0 | openssl-3 | before 3.5.0-160000.4.1 | 3.5.0-160000.4.1 |
Same product
openssl: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows…KEV90Now
- CVE-2021-3711SM2 Decryption Buffer Overflow65This week
- CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code…65This week
Published before and after this one in the same product
- ← EarlierCVE-2025-4575May 22, 2025 · The x509 application adds trusted use instead of rejected use26Monitor
- ← EarlierCVE-2025-9230Sep 30, 2025 · Out-of-bounds read & write in RFC 3211 KEK Unwrap40Plan
- Later →CVE-2025-11187Jan 27, 2026 · Improper validation of PBMAC1 parameters in PKCS#12 MAC verification26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| OpenSSL OpenSSL | 3.0.18 | Vendor (CNA) |
| OpenSSL OpenSSL | 3.2.6 | Vendor (CNA) |
| OpenSSL OpenSSL | 3.3.5 | Vendor (CNA) |
| OpenSSL OpenSSL | 3.4.3 | Vendor (CNA) |
| OpenSSL OpenSSL | 3.5.4 | Vendor (CNA) |
| azl3 openssl 3.3.3-3 on Azure Linux 3.0 | 3.3.5-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| alpine:openssl | 3.0.19-r0 · Alpine:v3.17 | Package registry (OSV) |
| debian:openssl | 3.0.17-1~deb12u3 · Debian:12 | Package registry (OSV) |
| opensuse:openssl-3 | 3.5.0-160000.4.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:regclient | 0.10.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:openssl | 0:3.5.6-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-config-fips | 0:3.5.6-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-devel | 0:3.5.6-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-devel-engine | 0:3.5.6-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-libs | 0:3.5.6-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-perl | 0:3.5.6-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| suse:openssl-3 | 3.5.0-160000.4.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Stanislav Fort (Aisle Research)reporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-92300 days apartOut-of-bounds read & write in RFC 3211 KEK Unwrap40Plan
- CVE-2024-9143349 days apartLow-level invalid GF(2^m) parameters lead to OOB memory access39Monitor
- CVE-2024-5535460 days apartSSL_select_next_proto buffer overread38Monitor
- CVE-2026-84782364 days apartDTLS Retransmits Handshake Messages From a Stale Buffer Offset32Monitor
- CVE-2026-28386189 days apartOut-of-bounds Read in AES-CFB-128 on X86-64 with AVX-512 Support30Monitor
- CVE-2026-9076252 days apartOut-of-Bounds Read in CMS Password-Based Decryption30Monitor
Not on record for this CVE: EPSS history · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (12 more)Show less
- github.com/openssl/openssl/commit/654dc11d23468a74fc8ea4672b702dd3feb7be4b
- github.com/openssl/openssl/commit/7cf21a30513c9e43c4bc3836c237cf086e194af3
- github.com/openssl/openssl/commit/89e790ac431125a4849992858490bed6b225eadf
- github.com/openssl/openssl/commit/bbf38c034cdabd0a13330abcc4855c866f53d2e0
- openssl-library.org/news/secadv/20250930.txt
- www.openwall.com/lists/oss-security/2025/09/30/5
- cert-portal.siemens.com/productcert/html/ssa-032379.html
- cert-portal.siemens.com/productcert/html/ssa-082556.html
- cert-portal.siemens.com/productcert/html/ssa-089022.html
- cert-portal.siemens.com/productcert/html/ssa-253495.html
- cert-portal.siemens.com/productcert/html/ssa-485750.html
- cert-portal.siemens.com/productcert/html/ssa-585531.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.