dbcve.org
ApisixApplication · Apache

CVE-2025-27446

HIGH · 7.8 CVSS v3.1 Published 2025-07-06
Fix available
A fix is available. Upgrade to after 0.5 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Incorrect Permission Assignment for Critical Resource vulnerability in Apache APISIX(java-plugin-runner). Local listening file permissions in APISIX plugin runner allow a local attacker to elevate privileges. This issue affects Apache APISIX(java-plugin-runner): from 0.2.0 through 0.5.0. Users are recommended to upgrade to version 0.6.0 or higher, which fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Apache APISIX java-plugin-runner versions 0.2.0 through 0.5.0 have incorrect file permissions on local listening files (likely Unix sockets or similar IPC mechanisms). These overly permissive permissions (possibly 0666) allow any local user to access these files, enabling a local attacker to potentially intercept communications or escalate privileges by interacting with the plugin runner's IPC interface.

MitigationUpgrade Apache APISIX java-plugin-runner to version 0.6.0 or higher, which contains the corrected file permissions. Verify that the new version properly restricts socket/file permissions to the running user or appropriate group.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ApisixApplication
Affected:>= 0.2, <= 0.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify java-plugin-runner installation
    Locate the java-plugin-runner installation directory and find its version identifier (version file, JAR metadata, or package manager listing)
    Affected if The installed version is 0.2.0, 0.3.0, 0.4.0, or 0.5.0 (any version from 0.2.0 through 0.5.0 inclusive)
  2. Locate IPC socket files
    Search for Unix socket files or named pipes in common runtime directories such as /tmp, the process working directory, /var/run, or the configured plugin runner socket path. Use 'find' or review the runner's configuration for socket path settings.
    Affected if Socket files created by the plugin runner exist in world-readable/writable locations
  3. Inspect socket file permissions
    Use 'ls -la' on the identified socket files to view their permission bits (e.g., ls -la /tmp/*.sock or ls -la /path/to/plugin-runner/run/)
    Affected if The socket files show permissions like 0666 (rw-rw-rw-) or any permission granting read/write access to others (o+rw or go+rw)
  4. Verify owner and group context
    Check the user and group ownership of the socket files using 'ls -la' and compare to the process owner running the java-plugin-runner
    Affected if Socket files are owned by the running user but world-accessible, or owned by a different user than the runner process
  5. Confirm plugin runner is in use
    Review Apache APISIX configuration to verify java-plugin-runner is enabled as a plugin runner (check apisix.yaml or config.yaml for runner configurations)
    Affected if java-plugin-runner is configured and active in the APISIX setup

A system is affected if java-plugin-runner versions 0.2.0 through 0.5.0 are installed and any Unix socket or IPC files created by the runner have permissions allowing access by other local users (such as 0666).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 0.5
Interim mitigation

Upgrade Apache APISIX java-plugin-runner to version 0.6.0 or higher, which contains the corrected file permissions. Verify that the new version properly restricts socket/file permissions to the running user or appropriate group.

Recommended fix High confidence

Apache APISIX java-plugin-runner >= 0.6.0

  1. 1. Identify the current version of Apache APISIX java-plugin-runner installed in your environment.
  2. 2. Download Apache APISIX java-plugin-runner version 0.6.0 or later from the official Apache repository.
  3. 3. Follow the standard upgrade procedure for Apache APISIX java-plugin-runner, ensuring to backup configuration files before proceeding.
  4. 4. Restart the java-plugin-runner service to apply the updated version.
  5. 5. Verify the upgrade was successful by checking the running version and confirming file permissions on local listening sockets are correctly restricted.
Caveat Review release notes for any configuration or API changes between 0.5.0 and 0.6.0; test in a non-production environment first.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Apisix Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27446 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-27446 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data