# CVE-2026-3209: fosrl Pangolin Role verifyApiKeyRoleAccess access control

> Attackers can bypass role-based access controls in fosrl Pangolin to gain unauthorized privileges, requiring an upgrade to the latest version.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Feb 2026
- **Updated:** 8 Mar 2026
- **Also known as:** GHSA-jv85-6mgr-3w99

## What is CVE-2026-3209?

CVE-2026-3209 is a medium-severity missing authorization vulnerability in fosrl Pangolin, published on 25 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been found in fosrl Pangolin up to 1.15.4-s.3. This affects the function verifyRoleAccess/verifyApiKeyRoleAccess of the component Role Handler. The manipulation leads to improper access controls. Remote exploitation of the attack is possible. The exploit has been disclosed to the public and may be used. Upgrading to version 1.15.4-s.4 mitigates this issue. The identifier of the patch is 5e37c4e85fae68e756be5019a28ca903b161fdd5. Upgrading the affected component is advised.

Weakness: CWE-284 (Improper Access Control), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-3209 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-3209 is a medium-severity missing authorization vulnerability in fosrl Pangolin, published on 25 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-3209 exists.

Affected product: fosrl Pangolin. 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-3209/ (Markdown: https://insights.sbomify.com/CVE-2026-3209/index.md)
```

## Sources

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

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