# CVE-2026-59284: Spring Cloud Commons no allow list for writable env actuator endpoint

> Attackers can modify arbitrary environment properties via the writable actuator endpoint, potentially leading to privilege escalation or code execution.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** CLSA-2026-1793201104, CLSA-2026-1793283345, GHSA-9w5v-hq8q-c6h7, ROOT-APP-MAVEN-CVE-2026-59284

## What is CVE-2026-59284?

CVE-2026-59284 is a medium-severity missing authorization vulnerability in Spring Cloud Commons, published on 27 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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

Weakness: CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes)

## Which versions are affected by CVE-2026-59284?

It affects 1 product.


Products: Broadcom Spring Cloud Commons.

## How do I fix CVE-2026-59284?

Upgrade to a fixed version.

## Is CVE-2026-59284 being exploited?

There is no known exploitation of CVE-2026-59284 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59284 and fix it if it is affected.

What it is: CVE-2026-59284 is a medium-severity missing authorization vulnerability in Spring Cloud Commons, published on 27 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-59284 in the wild and no public exploit code.

Affected product: Spring Cloud Commons. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-59284/ (Markdown: https://insights.sbomify.com/CVE-2026-59284/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59284
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59284
- OSV: https://osv.dev/vulnerability/CVE-2026-59284

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-59284/
Summaries are generated and may contain mistakes; the official description above is the record.