CVE-2025-8700: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-2x9q-pf3q-cg3c
Share
CWE-497
Published
Advisory Summary

CVE-2025-8700 is a MODERATE security vulnerability vulnerability (CWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.. Remediation is available in the latest vendor maintenance releases.

CVE-2025-8700 at a Glance

CVE Identifier CVE-2025-8700
GHSA Identifier GHSA-2x9q-pf3q-cg3c
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2025-8700

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2025-8700, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere, where the product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Invoice Ninja's configuration on macOS, specifically the presence of entitlement "com.apple.security.get-task-allow", allows local attackers with unprivileged access (e.g. via a malicious application) to attach a debugger, read or modify the process memory, inject code in the application's context despite being signed with Hardened Runtime and bypass Transparency, Consent, and Control (TCC). Acquired resource access is limited to previously granted permissions by the user. Access to other resources beyond granted permissions requires user interaction with a system prompt asking for permission. According to Apple documentation, when a non-root user runs an app with the debugging tool entitlement, the system presents an authorization dialog asking for a system administrator's credentials. Since there is no prompt when the target process has "get-task-allow" entitlement, the presence of this entitlement was decided to be treated as a vulnerability because it removes one step needed to perform an attack. This issue was fixed in version 5.0.175

References

NVD — CVE-2025-8700 NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-8700
cert.pl/en/posts/2025/08/tc... WEB
https://cert.pl/en/posts/2025/08/tcc-bypass
invoiceninja.com WEB
https://invoiceninja.com

Frequently Asked Questions

What is CVE-2025-8700?
CVE-2025-8700 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2025-8700?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2025-8700?
CVE-2025-8700 is classified under CWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere (The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.).
How can I check Maven dependencies for CVE-2025-8700?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2x9q-pf3q-cg3c",
  "modified" : "2025-08-26T15:31:01Z",
  "published" : "2025-08-26T15:31:01Z",
  "aliases" : [ "CVE-2025-8700" ],
  "details" : "Invoice Ninja's configuration on macOS, specifically the presence of entitlement \"com.apple.security.get-task-allow\", allows local attackers with unprivileged access (e.g. via a malicious application) to attach a debugger, read or modify the process memory, inject code in the application's context despite being signed with Hardened Runtime and bypass Transparency, Consent, and Control (TCC). Acquired resource access is limited to previously granted permissions by the user. Access to other resources beyond granted permissions requires user interaction with a system prompt asking for permission.\n\nAccording to Apple documentation, when a non-root user runs an app with the debugging tool entitlement, the system presents an authorization dialog asking for a system administrator's credentials. Since there is no prompt when the target process has \"get-task-allow\" entitlement, the presence of this entitlement was decided to be treated as a vulnerability because it removes one step needed to perform an attack.\n\n\nThis issue was fixed in version 5.0.175",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-8700"
  }, {
    "type" : "WEB",
    "url" : "https://cert.pl/en/posts/2025/08/tcc-bypass"
  }, {
    "type" : "WEB",
    "url" : "https://invoiceninja.com"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-497" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2025-08-26T13:15:33Z"
  }
}