Apache Commons VFS Exposure of Sensitive Information to an Unauthorized Actor

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2025-30474: 0.89% estimated exploitation activity in the next 30 days; percentile 59.35 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Commons VFS. The FtpFileObject class can throw an exception when a file is not found, revealing the original URI in its message, which may include a password. The fix is to mask the password in the exception message This issue affects Apache Commons VFS: before 2.10.0. Users are recommended to upgrade to version 2.10.0, which fixes the issue.

Published by the source

23 Mar 2025, 15:30 UTC

Last modified by the source

25 Mar 2025, 03:23 UTC

Source last checked

26 Oct 2026, 16:35 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3936-3gx6-49c4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-30474

Advisory: Apache Commons VFS Exposure of Sensitive Information to an Unauthorized Actor
IDs: CVE-2025-30474, GHSA-3936-3gx6-49c4
Record: https://patchnext.com/advisories/cve-2025-30474 (revision 1, source checked 26 Oct 2026, 16:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.commons:commons-vfs2 2.10.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.commons:commons-vfs2: affected < 2.10.0; fixed in 2.10.0

## Suggested inspection (read-only)
- Maven org.apache.commons:commons-vfs2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.commons:commons-vfs2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3936-3gx6-49c4 (GitHub-reviewed advisory GHSA-3936-3gx6-49c4 lists affected ranges: Maven org.apache.commons:commons-vfs2 >=0 <2.10.0)

Commands are suggestions: review each one before running it.