# CVE-2025-45616: BRCC Incorrect Access Control vulnerability

> Attackers can gain admin rights via crafted requests to the admin API due to incorrect access control in the brcc library.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 May 2025
- **Updated:** 6 May 2025
- **Also known as:** GHSA-w7xj-pj5f-8pwh

## What is CVE-2025-45616?

CVE-2025-45616 is a critical missing authorization vulnerability in n/a, published on 5 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incorrect access control in the /admin/** API of brcc v1.2.0 allows attackers to gain access to Admin rights via a crafted request.

Weakness: CWE-284 (Improper Access Control)

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

2 open source packages ship an affected version, including com.baidu.mapp:brcc-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.baidu.mapp:brcc-core` | Maven | All versions to 1.2.0 | None |
| `com.baidu.mapp:brcc-core` | Maven | All versions to 1.2.0 | None |

Products: Baidu Brcc.

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

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

## Is CVE-2025-45616 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-45616 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-45616 is a critical missing authorization vulnerability in n/a, published on 5 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-45616 exists.

Affected packages and fixed versions:
- com.baidu.mapp:brcc-core (Maven): affected all versions up to 1.2.0; no fix listed
- com.baidu.mapp:brcc-core (Maven): affected all versions up to 1.2.0; no fix listed

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-45616/ (Markdown: https://insights.sbomify.com/CVE-2025-45616/index.md)
```

## Sources

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

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