# CVE-2025-4971: Broadcom Automic Automation Agent Unix privilege escalation

> Low-privileged users with execution rights can escalate privileges in Broadcom Automic Automation Agent Unix.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 May 2025
- **Updated:** 20 May 2025
- **Also known as:** GHSA-7hj6-h929-jq92

## What is CVE-2025-4971?

CVE-2025-4971 is a high-severity vulnerability in Broadcom Automic Automation, published on 19 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Broadcom Automic
Automation Agent Unix versions <
24.3.0 HF4 and < 21.0.13 HF1 allow low privileged users who have execution
rights on the agent executable to escalate their privileges.

Weakness: CWE-426 (Untrusted Search Path)

## Which versions are affected by CVE-2025-4971?


## How do I fix CVE-2025-4971?

No fix has been published for CVE-2025-4971 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-4971 being exploited?

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

Public exploit code:

- Automic Agent 24.3.0 HF4 - Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-4971 and fix it if it is affected.

What it is: CVE-2025-4971 is a high-severity vulnerability in Broadcom Automic Automation, published on 19 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-4971 in the wild and no public exploit code.

Affected product: Broadcom Automic Automation. 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-2025-4971/ (Markdown: https://insights.sbomify.com/CVE-2025-4971/index.md)
```

## Sources

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

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