BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-9232High confidence

Out-of-bounds read in HTTP client no_proxy handling

OpenSSL · OpenSSL

Official source article: Siemens SSA-082556 ↗. Check the applicable product and release in the original source.

5.9MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 2.00% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs OpenSSL OpenSSL and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

7 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · mainopensslVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.3.5.4-r0Alpine Security Database ↗Source updated 23 Oct 2026
Alpine v3.22v3.22 · mainopensslVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.3.5.4-r0Alpine Security Database ↗Source updated 23 Oct 2026
Alpine v3.21v3.21 · mainopensslVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.3.3.5-r0Alpine Security Database ↗Source updated 23 Oct 2026
Debian trixietrixie · sourceopensslVendor fix publishedDebian records a fixed source-package version for this release.3.5.1-1+deb13u1Debian Security Tracker ↗Source updated 24 Oct 2026
Debian bookwormbookworm · sourceopensslVendor fix publishedDebian records a fixed source-package version for this release.3.0.17-1~deb12u3Debian Security Tracker ↗Source updated 24 Oct 2026
Debian forkyforky · sourceopensslVendor fix publishedDebian records a fixed source-package version for this release.3.5.4-1Debian Security Tracker ↗Source updated 24 Oct 2026
Debian sidsid · sourceopensslVendor fix publishedDebian records a fixed source-package version for this release.3.5.4-1Debian Security Tracker ↗Source updated 24 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

8 current
SSA-082556 · CSAF 2.0 · revision 8 · interimSiemens ProductCERTCVE-2025-9232
5 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.5
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.5
Summary
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.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
CVE-2025-9232 · CSAF 2.0 · revision 27 · interimSUSE Product Security TeamCVE-2025-9232
848 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • openssl as component of SLES-LTSS-TERADATA 15 SP2
  • openssl-1_0_0 as component of SLES-LTSS-TERADATA 15 SP2
  • openssl-1_1 as component of SLES-LTSS-TERADATA 15 SP2
  • libopenssl-1_1-devel as component of SUSE Linux Enterprise Desktop 15 SP6
  • libopenssl-3-devel as component of SUSE Linux Enterprise Desktop 15 SP6
  • libopenssl-3-fips-provider as component of SUSE Linux Enterprise Desktop 15 SP6
  • libopenssl-3-fips-provider-32bit as component of SUSE Linux Enterprise Desktop 15 SP6
  • libopenssl-devel as component of SUSE Linux Enterprise Desktop 15 SP6
  • libopenssl-fips-provider as component of SUSE Linux Enterprise Desktop 15 SP6
  • libopenssl1_1 as component of SUSE Linux Enterprise Desktop 15 SP6
  • libopenssl1_1-32bit as component of SUSE Linux Enterprise Desktop 15 SP6
  • libopenssl3 as component of SUSE Linux Enterprise Desktop 15 SP6
Summary
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.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2025-9232 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityopenssl: Out-of-bounds read in HTTP client no_proxy handling
23 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • edk2-aarch64 as a component of Red Hat Enterprise Linux 10
  • edk2-ovmf as a component of Red Hat Enterprise Linux 10
  • edk2-tools as a component of Red Hat Enterprise Linux 10
  • edk2-tools-doc as a component of Red Hat Enterprise Linux 10
  • edk2.src as a component of Red Hat Enterprise Linux 10
  • openssl as a component of Red Hat Enterprise Linux 10
  • openssl-devel as a component of Red Hat Enterprise Linux 10
  • openssl-libs as a component of Red Hat Enterprise Linux 10
  • openssl-perl as a component of Red Hat Enterprise Linux 10
  • openssl.src as a component of Red Hat Enterprise Linux 10
  • edk2-aarch64 as a component of Red Hat Enterprise Linux 9
  • edk2-ovmf as a component of Red Hat Enterprise Linux 9
Summary
A flaw was found in the OpenSSL HTTP client API no_proxy handling. This vulnerability allows an application level denial of service (application crash) via an attacker-controlled IPv6 URL when the no_proxy environment variable is set.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
SSA-585531 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-585531: Multiple Vulnerabilities in SIDIS Secured SmartPlug before V7.26.0310
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SIDIS Secured SmartPlug < V7.26.0310
Summary
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.
Remediation
Update to V7.26.0310 or later version
SSA-253495 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-253495: Multiple Vulnerabilities in SINEC OS before V4.0
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • RUGGEDCOM RST2428P (6GK6242-6PA00)
Summary
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.
Remediation
Update to V4.0 or later version
SSA-032379 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-032379: Multiple Vulnerabilities in SIMATIC CN 4100 Before V5.0
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SIMATIC CN 4100
Summary
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.
Remediation
Update to V5.0 or later version
SSA-485750 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-485750: Multiple Vulnerabilities in SIDIS Prime Before V4.0.800
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SIDIS Prime
Summary
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.
Remediation
Update to V4.0.800 or later version
SSA-089022 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-089022: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.3
16 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • RUGGEDCOM RST2428P (6GK6242-6PA00)
  • SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
  • SCALANCE XCH328 (6GK5328-4TS01-2EC2)
  • SCALANCE XCM324 (6GK5324-8TS01-2AC2)
  • SCALANCE XCM328 (6GK5328-4TS01-2AC2)
  • SCALANCE XCM332 (6GK5332-0GA01-2AC2)
  • SCALANCE XRH334 (24 V DC, 8xFO, CC) (6GK5334-2TS01-2ER3)
  • SCALANCE XRM334 (230 V AC, 12xFO) (6GK5334-3TS01-3AR3)
  • SCALANCE XRM334 (230 V AC, 8xFO) (6GK5334-2TS01-3AR3)
  • SCALANCE XRM334 (230V AC, 2x10G, 24xSFP, 8xSFP+) (6GK5334-5TS01-3AR3)
  • SCALANCE XRM334 (24 V DC, 12xFO) (6GK5334-3TS01-2AR3)
  • SCALANCE XRM334 (24 V DC, 8xFO) (6GK5334-2TS01-2AR3)
Summary
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.
Remediation
Update to V3.3 or later version
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-31727

No EUVD known-exploited evidence

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.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
5.9 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

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.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Out-of-bounds Read → disrupt the affected service
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-125 ↗

CWE-125: Out-of-bounds Read. The product reads data past the end, or before the beginning, of the intended buffer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedDenial of serviceCWE-125
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2025-31727Official EUVD mapping

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.

Official EUVD record ↗
BSI · German · WID-SEC-2026-0647SAP Patchday März 2026: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in SAP Software ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Cross-Site-Scripting-Angriffe durchzuführen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder andere, nicht näher spezifizierte Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2025-2166OpenSSL und LibreSSL: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in OpenSSL und LibreSSL ausnutzen, um potentiell beliebigen Code auszuführen, einen Denial of Service-Zustand zu verursachen und vertrauliche Informationen offenzulegen.

Official advisory ↗
Canadian Centre for Cyber Security · English · AV25-636[Control systems] SSL security advisory (AV25-636)

On September 30, 2025, OpenSSL published security advisories to address vulnerabilities in the following product:

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251001Security Bulletin 01 Oct 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 01 Oct 2025, published on 1 October 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CISA · English · ICSA-26-202-04Siemens SIDIS Secured SmartPlug

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.

Official advisory ↗
CISA · English · ICSA-26-188-05Siemens SINEC OS

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.

Official advisory ↗
CISA · English · ICSA-26-134-10Siemens SIMATIC

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.

Official advisory ↗
CISA · English · ICSA-26-071-03Siemens SIDIS Prime

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.

Official advisory ↗
CISA · English · ICSA-26-043-06Siemens SINEC OS

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.

Official advisory ↗
CISA · English · ICSA-25-162-05Siemens SIMATIC S7-1500 CPU family

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.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1351Avis du CERT-FR

ecord?id=CVE-2025-15224 Référence CVE CVE-2025-15467 https://www.cve.org/CVERecord?id=CVE-2025-15467 Référence CVE CVE-2025-68160 https://www.cve.org/CVERecord?id=CVE-2025-68160 Référence CVE CVE-2025-69418 https://www.cve.org/CVERecord?id=CVE-2025-69418 Référence CVE CVE-2025-69419 https://www.cve.org/CVERecord?id=CVE-2025-69419 Référence CVE CVE-2025-69420 https://www.cve.org/CVERecord?id=CVE-2025-69420 Référence CVE CVE-2025-69421 https://www.cve.org/CVERecord?id=CVE-2025-69421 Référence CVE CVE-2025-9086 https://www.cve.org/CVERecord?id=CVE-2025-9086 Référence CVE CVE-2025-9230 https://www.cve.org/CVERecord?id=CVE-2025-9230 Référence CVE CVE-2025-9232 https://www.cve.org/CVERecord?id=CVE-2025-9232 Référence CVE CVE-2026-101513 https://www.cve.org/CVERecord?id=CVE-2026-101513 Référence CVE CVE-2026-101607 https://www.cve.org/CVERecord?id=CVE-2026-101607 Référence CVE CVE-2026-101608 https://www.cve.org/CVERecord?id=CVE-2026-101608 Référence CVE CVE-2026-101609 https://www.cve.org/CVERecord?id=CVE-2026-101609 Référence CVE CVE-2026-101610 https://www.cve.org/CVERecord?id=CVE-2026-101610 Référence CVE CVE-2026-101611 https://www.cve.org/CVERecord?id=CVE-2026-101611 Référence CVE CVE-2026-101612 https://www.cve.org/CVERecord?id=CVE-2026-101612 Référence CVE CVE-2026-101613 https://www.cve.org

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0627Multiples vulnérabilités dans les produits Splunk

CVERecord?id=CVE-2025-69277 Référence CVE CVE-2025-69418 https://www.cve.org/CVERecord?id=CVE-2025-69418 Référence CVE CVE-2025-69419 https://www.cve.org/CVERecord?id=CVE-2025-69419 Référence CVE CVE-2025-69420 https://www.cve.org/CVERecord?id=CVE-2025-69420 Référence CVE CVE-2025-69421 https://www.cve.org/CVERecord?id=CVE-2025-69421 Référence CVE CVE-2025-7338 https://www.cve.org/CVERecord?id=CVE-2025-7338 Référence CVE CVE-2025-8194 https://www.cve.org/CVERecord?id=CVE-2025-8194 Référence CVE CVE-2025-8291 https://www.cve.org/CVERecord?id=CVE-2025-8291 Référence CVE CVE-2025-9086 https://www.cve.org/CVERecord?id=CVE-2025-9086 Référence CVE CVE-2025-9232 https://www.cve.org/CVERecord?id=CVE-2025-9232 Référence CVE CVE-2025-9820 https://www.cve.org/CVERecord?id=CVE-2025-9820 Référence CVE CVE-2026-0865 https://www.cve.org/CVERecord?id=CVE-2026-0865 Référence CVE CVE-2026-0965 https://www.cve.org/CVERecord?id=CVE-2026-0965 Référence CVE CVE-2026-0967 https://www.cve.org/CVERecord?id=CVE-2026-0967 Référence CVE CVE-2026-0968 https://www.cve.org/CVERecord?id=CVE-2026-0968 Référence CVE CVE-2026-1225 https://www.cve.org/CVERecord?id=CVE-2026-1225 Référence CVE CVE-2026-1584 https://www.cve.org/CVERecord?id=CVE-2026-1584 Référence CVE CVE-2026-1605 https://www.cve.org/CVERecord?id=CVE-2026-1605 Ré

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0565Multiples vulnérabilités dans les produits Siemens

org/CVERecord?id=CVE-2025-55754 Référence CVE CVE-2025-6021 https://www.cve.org/CVERecord?id=CVE-2025-6021 Référence CVE CVE-2025-6052 https://www.cve.org/CVERecord?id=CVE-2025-6052 Référence CVE CVE-2025-61748 https://www.cve.org/CVERecord?id=CVE-2025-61748 Référence CVE CVE-2025-61795 https://www.cve.org/CVERecord?id=CVE-2025-61795 Référence CVE CVE-2025-7425 https://www.cve.org/CVERecord?id=CVE-2025-7425 Référence CVE CVE-2025-8916 https://www.cve.org/CVERecord?id=CVE-2025-8916 Référence CVE CVE-2025-9230 https://www.cve.org/CVERecord?id=CVE-2025-9230 Référence CVE CVE-2025-9231 https://www.cve.org/CVERecord?id=CVE-2025-9231 Référence CVE CVE-2025-9232 https://www.cve.org/CVERecord?id=CVE-2025-9232 Référence CVE CVE-2025-9820 https://www.cve.org/CVERecord?id=CVE-2025-9820 Référence CVE CVE-2026-21925 https://www.cve.org/CVERecord?id=CVE-2026-21925 Référence CVE CVE-2026-21932 https://www.cve.org/CVERecord?id=CVE-2026-21932 Référence CVE CVE-2026-21933 https://www.cve.org/CVERecord?id=CVE-2026-21933 Référence CVE CVE-2026-21945 https://www.cve.org/CVERecord?id=CVE-2026-21945 Référence CVE CVE-2026-21947 https://www.cve.org/CVERecord?id=CVE-2026-21947 Référence CVE CVE-2026-22924 https://www.cve.org/CVERecord?id=CVE-2026-22924 Référence CVE CVE-2026-22925 https://www.cve.org/CVERecord?id=CVE

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

.cve.org/CVERecord?id=CVE-2025-7519 Référence CVE CVE-2025-8194 https://www.cve.org/CVERecord?id=CVE-2025-8194 Référence CVE CVE-2025-8277 https://www.cve.org/CVERecord?id=CVE-2025-8277 Référence CVE CVE-2025-8291 https://www.cve.org/CVERecord?id=CVE-2025-8291 Référence CVE CVE-2025-8677 https://www.cve.org/CVERecord?id=CVE-2025-8677 Référence CVE CVE-2025-8746 https://www.cve.org/CVERecord?id=CVE-2025-8746 Référence CVE CVE-2025-8941 https://www.cve.org/CVERecord?id=CVE-2025-8941 Référence CVE CVE-2025-9230 https://www.cve.org/CVERecord?id=CVE-2025-9230 Référence CVE CVE-2025-9231 https://www.cve.org/CVERecord?id=CVE-2025-9231 Référence CVE CVE-2025-9232 https://www.cve.org/CVERecord?id=CVE-2025-9232 Référence CVE CVE-2025-9301 https://www.cve.org/CVERecord?id=CVE-2025-9301 Référence CVE CVE-2025-9403 https://www.cve.org/CVERecord?id=CVE-2025-9403 Référence CVE CVE-2025-9820 https://www.cve.org/CVERecord?id=CVE-2025-9820 Référence CVE CVE-2026-0964 https://www.cve.org/CVERecord?id=CVE-2026-0964 Référence CVE CVE-2026-0965 https://www.cve.org/CVERecord?id=CVE-2026-0965 Référence CVE CVE-2026-0966 https://www.cve.org/CVERecord?id=CVE-2026-0966 Référence CVE CVE-2026-0967 https://www.cve.org/CVERecord?id=CVE-2026-0967 Référence CVE CVE-2026-0968 https://www.cve.org/CVERecord?id=CVE-2026-0968 Ré

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

e.org/CVERecord?id=CVE-2025-71237 Référence CVE CVE-2025-71238 https://www.cve.org/CVERecord?id=CVE-2025-71238 Référence CVE CVE-2025-7519 https://www.cve.org/CVERecord?id=CVE-2025-7519 Référence CVE CVE-2025-8277 https://www.cve.org/CVERecord?id=CVE-2025-8277 Référence CVE CVE-2025-8677 https://www.cve.org/CVERecord?id=CVE-2025-8677 Référence CVE CVE-2025-8746 https://www.cve.org/CVERecord?id=CVE-2025-8746 Référence CVE CVE-2025-8941 https://www.cve.org/CVERecord?id=CVE-2025-8941 Référence CVE CVE-2025-9230 https://www.cve.org/CVERecord?id=CVE-2025-9230 Référence CVE CVE-2025-9231 https://www.cve.org/CVERecord?id=CVE-2025-9231 Référence CVE CVE-2025-9232 https://www.cve.org/CVERecord?id=CVE-2025-9232 Référence CVE CVE-2025-9301 https://www.cve.org/CVERecord?id=CVE-2025-9301 Référence CVE CVE-2025-9403 https://www.cve.org/CVERecord?id=CVE-2025-9403 Référence CVE CVE-2025-9820 https://www.cve.org/CVERecord?id=CVE-2025-9820 Référence CVE CVE-2026-0964 https://www.cve.org/CVERecord?id=CVE-2026-0964 Référence CVE CVE-2026-0965 https://www.cve.org/CVERecord?id=CVE-2026-0965 Référence CVE CVE-2026-0966 https://www.cve.org/CVERecord?id=CVE-2026-0966 Référence CVE CVE-2026-0967 https://www.cve.org/CVERecord?id=CVE-2026-0967 Référence CVE CVE-2026-0968 https://www.cve.org/CVERecord?id=CVE-2026-0968 Ré

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0281Multiples vulnérabilités dans les produits Splunk

.cve.org/CVERecord?id=CVE-2025-6965 Référence CVE CVE-2025-8114 https://www.cve.org/CVERecord?id=CVE-2025-8114 Référence CVE CVE-2025-8291 https://www.cve.org/CVERecord?id=CVE-2025-8291 Référence CVE CVE-2025-8556 https://www.cve.org/CVERecord?id=CVE-2025-8556 Référence CVE CVE-2025-8885 https://www.cve.org/CVERecord?id=CVE-2025-8885 Référence CVE CVE-2025-8916 https://www.cve.org/CVERecord?id=CVE-2025-8916 Référence CVE CVE-2025-9086 https://www.cve.org/CVERecord?id=CVE-2025-9086 Référence CVE CVE-2025-9230 https://www.cve.org/CVERecord?id=CVE-2025-9230 Référence CVE CVE-2025-9231 https://www.cve.org/CVERecord?id=CVE-2025-9231 Référence CVE CVE-2025-9232 https://www.cve.org/CVERecord?id=CVE-2025-9232 Référence CVE CVE-2025-9714 https://www.cve.org/CVERecord?id=CVE-2025-9714 Référence CVE CVE-2025-9820 https://www.cve.org/CVERecord?id=CVE-2025-9820 Référence CVE CVE-2025-9951 https://www.cve.org/CVERecord?id=CVE-2025-9951 Référence CVE CVE-2026-20162 https://www.cve.org/CVERecord?id=CVE-2026-20162 Référence CVE CVE-2026-20163 https://www.cve.org/CVERecord?id=CVE-2026-20163 Référence CVE CVE-2026-20164 https://www.cve.org/CVERecord?id=CVE-2026-20164 Référence CVE CVE-2026-20165 https://www.cve.org/CVERecord?id=CVE-2026-20165 Référence CVE CVE-2026-20166 https://www.cve.org/CVERecord?id=CVE-202

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0266Multiples vulnérabilités dans VMware Tanzu

ord?id=CVE-2025-61730 Référence CVE CVE-2025-61731 https://www.cve.org/CVERecord?id=CVE-2025-61731 Référence CVE CVE-2025-61732 https://www.cve.org/CVERecord?id=CVE-2025-61732 Référence CVE CVE-2025-62813 https://www.cve.org/CVERecord?id=CVE-2025-62813 Référence CVE CVE-2025-64118 https://www.cve.org/CVERecord?id=CVE-2025-64118 Référence CVE CVE-2025-68119 https://www.cve.org/CVERecord?id=CVE-2025-68119 Référence CVE CVE-2025-68121 https://www.cve.org/CVERecord?id=CVE-2025-68121 Référence CVE CVE-2025-68972 https://www.cve.org/CVERecord?id=CVE-2025-68972 Référence CVE CVE-2025-7039 https://www.cve.org/CVERecord?id=CVE-2025-7039 Référence CVE CVE-2025-9232 https://www.cve.org/CVERecord?id=CVE-2025-9232 Référence CVE CVE-2025-9820 https://www.cve.org/CVERecord?id=CVE-2025-9820 Référence CVE CVE-2026-0861 https://www.cve.org/CVERecord?id=CVE-2026-0861 Référence CVE CVE-2026-0915 https://www.cve.org/CVERecord?id=CVE-2026-0915 Référence CVE CVE-2026-0988 https://www.cve.org/CVERecord?id=CVE-2026-0988 Référence CVE CVE-2026-0989 https://www.cve.org/CVERecord?id=CVE-2026-0989 Référence CVE CVE-2026-0990 https://www.cve.org/CVERecord?id=CVE-2026-0990 Référence CVE CVE-2026-0992 https://www.cve.org/CVERecord?id=CVE-2026-0992 Référence CVE CVE-2026-1484 https://www.cve.org/CVERecord?id=CVE-2026-1484 Ré

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0256Multiples vulnérabilités dans les produits SAP

De multiples vulnérabilités ont été découvertes dans les produits SAP. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et une injection SQL (SQLi).

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0199Multiples vulnérabilités dans les produits VMware

.cve.org/CVERecord?id=CVE-2025-8058 Référence CVE CVE-2025-8194 https://www.cve.org/CVERecord?id=CVE-2025-8194 Référence CVE CVE-2025-8291 https://www.cve.org/CVERecord?id=CVE-2025-8291 Référence CVE CVE-2025-8556 https://www.cve.org/CVERecord?id=CVE-2025-8556 Référence CVE CVE-2025-8732 https://www.cve.org/CVERecord?id=CVE-2025-8732 Référence CVE CVE-2025-8916 https://www.cve.org/CVERecord?id=CVE-2025-8916 Référence CVE CVE-2025-8941 https://www.cve.org/CVERecord?id=CVE-2025-8941 Référence CVE CVE-2025-9086 https://www.cve.org/CVERecord?id=CVE-2025-9086 Référence CVE CVE-2025-9230 https://www.cve.org/CVERecord?id=CVE-2025-9230 Référence CVE CVE-2025-9232 https://www.cve.org/CVERecord?id=CVE-2025-9232 Référence CVE CVE-2025-9714 https://www.cve.org/CVERecord?id=CVE-2025-9714 Référence CVE CVE-2026-0672 https://www.cve.org/CVERecord?id=CVE-2026-0672 Référence CVE CVE-2026-0861 https://www.cve.org/CVERecord?id=CVE-2026-0861 Référence CVE CVE-2026-0865 https://www.cve.org/CVERecord?id=CVE-2026-0865 Référence CVE CVE-2026-0915 https://www.cve.org/CVERecord?id=CVE-2026-0915 Référence CVE CVE-2026-0988 https://www.cve.org/CVERecord?id=CVE-2026-0988 Référence CVE CVE-2026-0989 https://www.cve.org/CVERecord?id=CVE-2026-0989 Référence CVE CVE-2026-0990 https://www.cve.org/CVERecord?id=CVE-2026-0990 Ré

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0112Multiples vulnérabilités dans les produits VMware

.cve.org/CVERecord?id=CVE-2025-8713 Référence CVE CVE-2025-8714 https://www.cve.org/CVERecord?id=CVE-2025-8714 Référence CVE CVE-2025-8715 https://www.cve.org/CVERecord?id=CVE-2025-8715 Référence CVE CVE-2025-8885 https://www.cve.org/CVERecord?id=CVE-2025-8885 Référence CVE CVE-2025-8916 https://www.cve.org/CVERecord?id=CVE-2025-8916 Référence CVE CVE-2025-8959 https://www.cve.org/CVERecord?id=CVE-2025-8959 Référence CVE CVE-2025-9086 https://www.cve.org/CVERecord?id=CVE-2025-9086 Référence CVE CVE-2025-9230 https://www.cve.org/CVERecord?id=CVE-2025-9230 Référence CVE CVE-2025-9231 https://www.cve.org/CVERecord?id=CVE-2025-9231 Référence CVE CVE-2025-9232 https://www.cve.org/CVERecord?id=CVE-2025-9232 Référence CVE CVE-2026-1484 https://www.cve.org/CVERecord?id=CVE-2026-1484 Référence CVE CVE-2026-1485 https://www.cve.org/CVERecord?id=CVE-2026-1485 Référence CVE CVE-2026-1489 https://www.cve.org/CVERecord?id=CVE-2026-1489 Référence CVE CVE-2026-21441 https://www.cve.org/CVERecord?id=CVE-2026-21441 Référence CVE CVE-2026-24842 https://www.cve.org/CVERecord?id=CVE-2026-24842 Référence CVE CVE-2026-24881 https://www.cve.org/CVERecord?id=CVE-2026-24881 Référence CVE CVE-2026-24882 https://www.cve.org/CVERecord?id=CVE-2026-24882 Référence CVE CVE-2026-24883 https://www.cve.org/CVERecord?id=CVE-202

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0101Multiples vulnérabilités dans les produits Siemens

ve.org/CVERecord?id=CVE-2025-4373 Référence CVE CVE-2025-4435 https://www.cve.org/CVERecord?id=CVE-2025-4435 Référence CVE CVE-2025-4516 https://www.cve.org/CVERecord?id=CVE-2025-4516 Référence CVE CVE-2025-4517 https://www.cve.org/CVERecord?id=CVE-2025-4517 Référence CVE CVE-2025-59375 https://www.cve.org/CVERecord?id=CVE-2025-59375 Référence CVE CVE-2025-6141 https://www.cve.org/CVERecord?id=CVE-2025-6141 Référence CVE CVE-2025-9086 https://www.cve.org/CVERecord?id=CVE-2025-9086 Référence CVE CVE-2025-9230 https://www.cve.org/CVERecord?id=CVE-2025-9230 Référence CVE CVE-2025-9231 https://www.cve.org/CVERecord?id=CVE-2025-9231 Référence CVE CVE-2025-9232 https://www.cve.org/CVERecord?id=CVE-2025-9232 Gestion détaillée du document le 29 janvier 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0070Multiples vulnérabilités dans Oracle MySQL

De multiples vulnérabilités ont été découvertes dans Oracle MySQL. Elles permettent à un attaquant de provoquer un déni de service à distance, une atteinte à la confidentialité des données et une atteinte à l'intégrité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0071Multiples vulnérabilités dans Oracle PeopleSoft

De multiples vulnérabilités ont été découvertes dans Oracle PeopleSoft. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et une atteinte à la confidentialité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1057Multiples vulnérabilités dans les produits VMware

e.org/CVERecord?id=CVE-2025-62426 Référence CVE CVE-2025-65106 https://www.cve.org/CVERecord?id=CVE-2025-65106 Référence CVE CVE-2025-6965 https://www.cve.org/CVERecord?id=CVE-2025-6965 Référence CVE CVE-2025-7709 https://www.cve.org/CVERecord?id=CVE-2025-7709 Référence CVE CVE-2025-8194 https://www.cve.org/CVERecord?id=CVE-2025-8194 Référence CVE CVE-2025-8732 https://www.cve.org/CVERecord?id=CVE-2025-8732 Référence CVE CVE-2025-9086 https://www.cve.org/CVERecord?id=CVE-2025-9086 Référence CVE CVE-2025-9230 https://www.cve.org/CVERecord?id=CVE-2025-9230 Référence CVE CVE-2025-9231 https://www.cve.org/CVERecord?id=CVE-2025-9231 Référence CVE CVE-2025-9232 https://www.cve.org/CVERecord?id=CVE-2025-9232 Référence CVE CVE-2025-9714 https://www.cve.org/CVERecord?id=CVE-2025-9714 Gestion détaillée du document le 02 décembre 2025 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0969Multiples vulnérabilités dans les produits VMware

.cve.org/CVERecord?id=CVE-2025-8885 Référence CVE CVE-2025-8916 https://www.cve.org/CVERecord?id=CVE-2025-8916 Référence CVE CVE-2025-8941 https://www.cve.org/CVERecord?id=CVE-2025-8941 Référence CVE CVE-2025-8961 https://www.cve.org/CVERecord?id=CVE-2025-8961 Référence CVE CVE-2025-9086 https://www.cve.org/CVERecord?id=CVE-2025-9086 Référence CVE CVE-2025-9092 https://www.cve.org/CVERecord?id=CVE-2025-9092 Référence CVE CVE-2025-9165 https://www.cve.org/CVERecord?id=CVE-2025-9165 Référence CVE CVE-2025-9230 https://www.cve.org/CVERecord?id=CVE-2025-9230 Référence CVE CVE-2025-9231 https://www.cve.org/CVERecord?id=CVE-2025-9231 Référence CVE CVE-2025-9232 https://www.cve.org/CVERecord?id=CVE-2025-9232 Référence CVE CVE-2025-9288 https://www.cve.org/CVERecord?id=CVE-2025-9288 Référence CVE CVE-2025-9340 https://www.cve.org/CVERecord?id=CVE-2025-9340 Référence CVE CVE-2025-9341 https://www.cve.org/CVERecord?id=CVE-2025-9341 Référence CVE CVE-2025-9390 https://www.cve.org/CVERecord?id=CVE-2025-9390 Référence CVE CVE-2025-9403 https://www.cve.org/CVERecord?id=CVE-2025-9403 Référence CVE CVE-2025-9640 https://www.cve.org/CVERecord?id=CVE-2025-9640 Référence CVE CVE-2025-9714 https://www.cve.org/CVERecord?id=CVE-2025-9714 Référence CVE CVE-2025-9900 https://www.cve.org/CVERecord?id=CVE-2025-9900 Ge

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0967Multiples vulnérabilités dans les produits VMware

.cve.org/CVERecord?id=CVE-2025-8194 Référence CVE CVE-2025-8291 https://www.cve.org/CVERecord?id=CVE-2025-8291 Référence CVE CVE-2025-8713 https://www.cve.org/CVERecord?id=CVE-2025-8713 Référence CVE CVE-2025-8714 https://www.cve.org/CVERecord?id=CVE-2025-8714 Référence CVE CVE-2025-8715 https://www.cve.org/CVERecord?id=CVE-2025-8715 Référence CVE CVE-2025-8885 https://www.cve.org/CVERecord?id=CVE-2025-8885 Référence CVE CVE-2025-8916 https://www.cve.org/CVERecord?id=CVE-2025-8916 Référence CVE CVE-2025-9230 https://www.cve.org/CVERecord?id=CVE-2025-9230 Référence CVE CVE-2025-9231 https://www.cve.org/CVERecord?id=CVE-2025-9231 Référence CVE CVE-2025-9232 https://www.cve.org/CVERecord?id=CVE-2025-9232 Gestion détaillée du document le 05 novembre 2025 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0938Multiples vulnérabilités dans les produits VMware

.cve.org/CVERecord?id=CVE-2025-7425 Référence CVE CVE-2025-8176 https://www.cve.org/CVERecord?id=CVE-2025-8176 Référence CVE CVE-2025-8194 https://www.cve.org/CVERecord?id=CVE-2025-8194 Référence CVE CVE-2025-8713 https://www.cve.org/CVERecord?id=CVE-2025-8713 Référence CVE CVE-2025-8714 https://www.cve.org/CVERecord?id=CVE-2025-8714 Référence CVE CVE-2025-8715 https://www.cve.org/CVERecord?id=CVE-2025-8715 Référence CVE CVE-2025-8941 https://www.cve.org/CVERecord?id=CVE-2025-8941 Référence CVE CVE-2025-9230 https://www.cve.org/CVERecord?id=CVE-2025-9230 Référence CVE CVE-2025-9231 https://www.cve.org/CVERecord?id=CVE-2025-9231 Référence CVE CVE-2025-9232 https://www.cve.org/CVERecord?id=CVE-2025-9232 Référence CVE CVE-2025-9288 https://www.cve.org/CVERecord?id=CVE-2025-9288 Référence CVE CVE-2025-9900 https://www.cve.org/CVERecord?id=CVE-2025-9900 Gestion détaillée du document le 30 octobre 2025 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0835Multiples vulnérabilités dans OpenSSL

De multiples vulnérabilités ont été découvertes dans OpenSSL. Elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et une atteinte à la confidentialité des données.

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0229Kwetsbaarheden verholpen in Siemens producten

Multiple OpenSSL vulnerabilities, including an out-of-bounds read in the HTTP client 'no_proxy' handling and timing side-channels in SM2 on ARM, affect various products causing denial of service and potential code execution in some cases.

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0147Kwetsbaarheden verholpen in Siemens-producten

Multiple OpenSSL vulnerabilities, including an out-of-bounds read in the HTTP client 'no_proxy' handling causing denial of service, affect various products such as Oracle Essbase, PeopleSoft, JD Edwards, SAP NetWeaver, and NetApp, with severity ranging from low to moderate.

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0091Kwetsbaarheden verholpen in SAP-producten

A low-severity out-of-bounds read vulnerability in OpenSSL HTTP client API occurs when the 'no_proxy' environment variable is set and the HTTP URL contains an IPv6 address, causing denial of service via application crash in multiple products including Oracle PeopleSoft and NetApp devices.

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0079Kwetsbaarheden verholpen in Siemens producten

A low-severity out-of-bounds read vulnerability in OpenSSL HTTP client API occurs when the 'no_proxy' environment variable is set and the HTTP URL contains an IPv6 address, causing denial of service via application crash in multiple products including Oracle PeopleSoft and NetApp devices.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
04

Evidence and provenance

Published 30 Sept 2025 · Last source change 15 Oct 2026, 01:02 UTC · CWE-125 · Out-of-bounds Read

CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-31727
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceCNA
NVD statusNVD not scheduled

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: removed remediation: access.redhat.com/CVE-2025-9232.
    Before
    remediation: access.redhat.com/CVE-2025-9232
    After
    no authoritative guidance recorded
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    3.5.0 < 3.5.4; 3.4.0 < 3.4.3; 3.3.3 < 3.3.5; 3.2.4 < 3.2.6; 3.0.16 < 3.0.18 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
    After
    OpenSSL: 3.5.0 < 3.5.4, 3.4.0 < 3.4.3, 3.3.3 < 3.3.5, 3.2.4 < 3.2.6, 3.0.16 < 3.0.18 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  3. Remediation statusRemediation status changed from Patch available to Awaiting fix.
    Before
    Patch available
    After
    Awaiting fix
    CNA ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    OpenSSL: 3.5.0 < 3.5.4, 3.4.0 < 3.4.3, 3.3.3 < 3.3.5, 3.2.4 < 3.2.6, 3.0.16 < 3.0.18 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    OpenSSL: 3.5.0 < 3.5.4, 3.4.0 < 3.4.3, 3.3.3 < 3.3.5, 3.2.4 < 3.2.6, 3.0.16 < 3.0.18 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
    Red Hat Product Security ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    3.5.0 < 3.5.4; 3.4.0 < 3.4.3; 3.3.3 < 3.3.5; 3.2.4 < 3.2.6; 3.0.16 < 3.0.18 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    3.5.0 < 3.5.4; 3.4.0 < 3.4.3; 3.3.3 < 3.3.5; 3.2.4 < 3.2.6; 3.0.16 < 3.0.18 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
    Red Hat Product Security ↗
  6. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  7. Affected versionsThe structured affected or fixed version information changed.
    Before
    edk2-aarch64 as a component of Red Hat Enterprise Linux 10; edk2-ovmf as a component of Red Hat Enterprise Linux 10; edk2-tools as a component of Red Hat Enterprise Linux 10; edk2-tools-doc as a component of Red Hat Enterprise Linux 10; edk2.src as a component of Red Hat Enterprise Linux 10; openssl as a component of Red Hat Enterprise Linux 10; openssl-devel as a component of Red Hat Enterprise Linux 10; openssl-libs as a component of Red Hat Enterprise Linux 10; openssl-perl as a component of Red Hat Enterprise Linux 10; openssl.src as a component of Red Hat Enterprise Linux 10; edk2-aarch64 as a component of Red Hat Enterprise Linux 9; edk2-ovmf as a component of Red Hat Enterprise Linux 9; edk2-tools as a component of Red Hat Enterprise Linux 9; edk2-tools-doc as a component of Red Hat Enterprise Linux 9; edk2.src as a component of Red Hat Enterprise Linux 9; openssl as a component of Red Hat Enterprise Linux 9; openssl-devel as a component of Red Hat Enterprise Linux 9; openssl-libs as a component of Red Hat Enterprise Linux 9; openssl-perl as a component of Red Hat Enterprise Linux 9; openssl.src as a component of Red Hat Enterprise Linux 9; openssl as a component of Red Hat JBoss Core Services; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4 · Fixed: openssl-main@aarch64 as a component of Red Hat Hardened Images; openssl-main@src as a component of Red Hat Hardened Images; openssl-main@x86_64 as a component of Red Hat Hardened Images
    After
    edk2-aarch64 as a component of Red Hat Enterprise Linux 10; edk2-ovmf as a component of Red Hat Enterprise Linux 10; edk2-tools as a component of Red Hat Enterprise Linux 10; edk2-tools-doc as a component of Red Hat Enterprise Linux 10; edk2.src as a component of Red Hat Enterprise Linux 10; openssl as a component of Red Hat Enterprise Linux 10; openssl-devel as a component of Red Hat Enterprise Linux 10; openssl-libs as a component of Red Hat Enterprise Linux 10; openssl-perl as a component of Red Hat Enterprise Linux 10; openssl.src as a component of Red Hat Enterprise Linux 10; edk2-aarch64 as a component of Red Hat Enterprise Linux 9; edk2-ovmf as a component of Red Hat Enterprise Linux 9; edk2-tools as a component of Red Hat Enterprise Linux 9; edk2-tools-doc as a component of Red Hat Enterprise Linux 9; edk2.src as a component of Red Hat Enterprise Linux 9; openssl as a component of Red Hat Enterprise Linux 9; openssl-devel as a component of Red Hat Enterprise Linux 9; openssl-libs as a component of Red Hat Enterprise Linux 9; openssl-perl as a component of Red Hat Enterprise Linux 9; openssl.src as a component of Red Hat Enterprise Linux 9; openssl as a component of Red Hat JBoss Core Services; openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4 · Fixed: openssl-main@aarch64 as a component of Red Hat Hardened Images; openssl-main@src as a component of Red Hat Hardened Images; openssl-main@x86_64 as a component of Red Hat Hardened Images
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-9232 · cve.blacktree.nl