CVE-2026-59284: There is no allow list for property keys when Spring Cloud Commons writable /actuator/env is enabled. Spring C

Routine

HIGH 7.6UPGRADE

CVE-2026-59284 is a high-severity flaw (CVSS 7.6) affecting spring cloud commons. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

There is no allow list for property keys when Spring Cloud Commons writable /actuator/env is enabled. Spring Cloud Commons 5.0.0 - 5.0.2 Spring Cloud Commons 4.3.0 - 4.3.3 Spring Cloud Commons 4.0.0 - 4.2.6 Spring Cloud Commons 3.1.10 and earlier

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.6 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	0.4% (top 63%)
CISA exploited list	No
Weakness	CWE-915
Published	2026-08-27
Last modified	2026-09-01

Publisher (CNA): VMware · Vendor: broadcom

Last updated 2026-09-01 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-08-27 20:17 UTCPublished CVE record published
2026-09-01 13:54 UTCUpdated Record last modified

broadcom spring cloud commons UPGRADE

Affected: < 3.1.11 · >= 4.0.0 and < 4.2.7 · >= 4.3.0 and < 4.3.4 · >= 5.0.0 and < 5.0.3

Fixed in: 3.1.11, 4.2.7, 4.3.4, 5.0.3

Safe to downgrade to: a release before 4.0.0

1. Check installed version

apt-cache policy spring-cloud-commons || rpm -q spring-cloud-commons || spring-cloud-commons --version

2. UPGRADE to 3.1.11 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade spring-cloud-commons

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade spring-cloud-commons

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 4.0.0 (Debian / Ubuntu)

apt-cache madison spring-cloud-commons sudo apt install spring-cloud-commons=<VERSION_BEFORE_4.0.0> sudo apt-mark hold spring-cloud-commons

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list spring-cloud-commons sudo dnf downgrade spring-cloud-commons-<VERSION_BEFORE_4.0.0> sudo dnf versionlock add spring-cloud-commons

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-59284?

spring cloud commons: upgrade to 3.1.11, 4.2.7, 4.3.4, 5.0.3. Exact commands for each OS are on this page.

Is CVE-2026-59284 being exploited?

CVE-2026-59284 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-59284 affect?

CVE-2026-59284 affects spring cloud commons. Severity is high (CVSS 7.6). There is no allow list for property keys when Spring Cloud Commons writable /actuator/env is enabled. Spring Cloud Commons 5.0.0 - 5.0.2 Spring Cloud Commons 4.3.0 - 4.3.3 Spring Cloud Commons 4.0.0 - 4.2.6 Spring Cloud Commons 3.1.10 and e

How urgent is CVE-2026-59284?

Priority 36/100. High severity

References

← Back to latest CVEs