# CVE-2026-42571: Privilege Escalation Attack affecting Pelican Web UI

> Authenticated users can gain admin privileges in the Pelican WebUI under certain configurations, allowing unauthorized administrative control.

- **Severity:** Critical 9.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-rpfr-x88x-xwcw, GO-2026-5632

## What is CVE-2026-42571?

CVE-2026-42571 is a critical vulnerability in PelicanPlatform pelican, published on 9 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Pelican is a platform for creating data federations. From versions 7.21.0 to before 7.21.5, 7.22.0 to before 7.22.3, 7.23.0 to before 7.23.3, and 7.24.0 to before 7.24.2, there is a a privilege escalation vulnerability affecting Pelican's Web User Interface (WebUI). This attack allows any user authenticated to the WebUI via OAuth to gain admin privileges under certain configurations. This issue has been patched in versions 7.21.5, 7.22.3, 7.23.3, and 7.24.2.

Weakness: CWE-863 (Incorrect Authorization)

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

3 open source packages ship an affected version, including github.com/pelicanplatform/pelican.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/pelicanplatform/pelican` | Go | All versions | 0.0.0-20260408120501-7f73b9c3e677 |
| `github.com/pelicanplatform/pelican` | Go | All versions | 0.0.0-20260408120501-7f73b9c3e677 |
| `github.com/pelicanplatform/pelican` | Go | All versions | 0.0.0-20260408120501-7f73b9c3e677 |

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

Upgrade github.com/pelicanplatform/pelican to 0.0.0-20260408120501-7f73b9c3e677 or later.

## Is CVE-2026-42571 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42571 is a critical vulnerability in PelicanPlatform pelican, published on 9 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-42571 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/pelicanplatform/pelican (Go): affected all versions; fixed in 0.0.0-20260408120501-7f73b9c3e677
- github.com/pelicanplatform/pelican (Go): affected all versions; fixed in 0.0.0-20260408120501-7f73b9c3e677
- github.com/pelicanplatform/pelican (Go): affected all versions; fixed in 0.0.0-20260408120501-7f73b9c3e677

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

## Sources

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

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