VulnerabilityPublished 9 Sep 2025

CVE-2025-42927: SAP NetWeaver AS Java (Adobe Document Service) · Dependency on Vulnerable Third-Party Component

Affects SAP NetWeaver AS Java (Adobe Document Service)Source CVE Database V5

Not known to be exploited · CVSS 3.4 Low.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

3.4Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

European organizations should implement a multi-layered mitigation strategy: 1) Conduct an inventory to identify all SAP NetWeaver AS Java instances running Adobe Document Service version ADSSAP 7.50. 2) Monitor SAP and OpenSSL vendor advisories closely for patches or updates addressing this vulnerability and apply them promptly once available. 3) Restrict and monitor high-privilege user accounts rigorously to reduce the risk of exploitation by insiders or compromised accounts. 4) Employ application whitelisting and integrity monitoring on SAP servers to detect unauthorized changes to system information. 5) Use network segmentation and strict access controls to limit local access to SAP servers, minimizing the attack surface for local exploits. 6) Regularly update and patch all third-party components, including OpenSSL, as part of a robust software supply chain security practice. 7) Implement comprehensive logging and alerting for suspicious activities related to SAP system modifications. These targeted actions go beyond generic advice by focusing on privilege management, component lifecycle, and proactive monitoring tailored to the SAP environment.

Description

SAP NetWeaver AS Java application uses Adobe Document Service, installed with a vulnerable version of OpenSSL.Successful exploitation of known vulnerabilities in the outdated OpenSSL library would allow user with high system privileges to access and modify system information.This vulnerability has a low impact on confidentiality and integrity, with no impact on availability.

Impact

For European organizations using SAP NetWeaver AS Java with the Adobe Document Service (version ADSSAP 7.50), this vulnerability poses a limited but tangible risk. Since exploitation requires high system privileges, the threat primarily concerns insider threats or attackers who have already breached initial defenses. The potential to access and modify system information could lead to unauthorized data manipulation or leakage of sensitive configuration details, undermining data integrity and confidentiality. Although availability is not impacted, the integrity compromise could affect business processes relying on SAP systems, which are critical in many European industries such as manufacturing, finance, and public sector services. Given SAP's widespread adoption across Europe, organizations must consider this vulnerability in their risk assessments, especially those with complex SAP landscapes and stringent compliance requirements like GDPR. The low severity suggests limited immediate risk, but the dependency on an outdated OpenSSL version could be a vector for chained attacks if combined with other vulnerabilities or privilege escalation techniques.

CWE-1395Dependency on Vulnerable Third-Party Component (opens in a new tab)
Class weaknessOWASP Top 10 A03:2025: Software Supply Chain Failures (opens in a new tab)
The product has a dependency on a third-party component that contains one or more known vulnerabilities.
Requirements · Policy
In some industries such as healthcare or technologies such as the cloud, it might be unclear about who is responsible for applying patches for third-party vulnerabilities: the vendor, the operator/customer, or a separate service.
Requirements
Require a Bill of Materials for all components and sub-components of the product. For software, require a Software Bill of Materials (SBOM).
Architecture and Design · Implementation · Integration · Manufacturing
Maintain a Bill of Materials for all components and sub-components of the product. For software, maintain a Software Bill of Materials (SBOM). According to, "An SBOM is a formal, machine-readable inventory of software components and dependencies, information about those components, and their hierarchical…
OWASP Cheat Sheets
OWASP Cheat Sheet Series: Dependency Graph SBOM (opens in a new tab)
OWASP Cheat Sheet Series: Vulnerable Dependency Management (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 9 Sep 2025, 02:32 UTC

WeaknessesCWE-1395

Technical details

References

Community reviews

Related threats