CVE-2025-48734: Apache Commons Improper Access Control vulnerability

Quick answers

Is CVE-2025-48734 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-48734 being exploited in the wild.

How severe is CVE-2025-48734?

Low severity, with a CVSS score of 3.1, published 28 May 2025.

Which products and versions are affected?

commons-beanutils:commons-beanutils (Maven) ECOSYSTEM:introduced=1.0,fixed=1.11.0; org.apache.commons:commons-beanutils2 (Maven) ECOSYSTEM:introduced=2.0.0-M1,fixed=2.0.0-M2.

Is there a fix for CVE-2025-48734?

Yes. commons-beanutils:commons-beanutils (Maven): upgrade to 1.11.0 or later; org.apache.commons:commons-beanutils2 (Maven): upgrade to 2.0.0-M2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2025-48734?

Check whether you run commons-beanutils:commons-beanutils (Maven) or org.apache.commons:commons-beanutils2 (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

• commons-beanutils:commons-beanutils (Maven): upgrade to 1.11.0 or later

  # set commons-beanutils:commons-beanutils to 1.11.0 in your pom.xml or build.gradle

• org.apache.commons:commons-beanutils2 (Maven): upgrade to 2.0.0-M2 or later

  # set org.apache.commons:commons-beanutils2 to 2.0.0-M2 in your pom.xml or build.gradle

Affected products

• commons-beanutils:commons-beanutils (Maven) ECOSYSTEM:introduced=1.0,fixed=1.11.0
• org.apache.commons:commons-beanutils2 (Maven) ECOSYSTEM:introduced=2.0.0-M1,fixed=2.0.0-M2

Identifiers

• CVE-2025-48734
• GHSA-wxr5-93ph-8wr9