← Back
CVE-2026-42571
Authorization Flaw in github.com/pelicanplatform/pelican (CVE-2026-42571)
Summary
vulnerability in github.com/pelicanplatform/pelican (CVE-2026-42571). Risk of unauthorized operations or information disclosure. Exploitable via ``Issuer.GroupSource``. Mitigation: upgrade to `0.0.0-20260408120501-7f73b9c3e677` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-42571** has been found in github.com/pelicanplatform/pelican.
Attackers can target a specific entry point like ``Issuer.GroupSource`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade github.com/pelicanplatform/pelican to **0.0.0-20260408120501-7f73b9c3e677** or later.
If unsure, ask your IT team or search "github.com/pelicanplatform/pelican CVE-2026-42571" on the vendor's site.
CVE-2026-42571 (github.com/pelicanplatform/pelican) — CWE-863 /
Attack surface: `Issuer.GroupSource` / `internal` / `Server.UIAdminUsers` / `Server.AdminGroups`
Patched: `0.0.0-20260408120501-7f73b9c3e677` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**incorrect authorization** (CWE-863) exists in github.com/pelicanplatform/pelican. Attackers reach the vulnerable code path via ``Issuer.GroupSource`` without authentication.
📍 Affected scope
github.com/pelicanplatform/pelican — . Attack surface: `Issuer.GroupSource` / `internal` / `Server.UIAdminUsers` / `Server.AdminGroups`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.0.0-20260408120501-7f73b9c3e677**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/pelicanplatform/pelican' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/pelicanplatform/pelican' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/pelicanplatform/pelican` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/pelicanplatform/pelican to 0.0.0-20260408120501-7f73b9c3e677ステージング環境で 0.0.0-20260408120501-7f73b9c3e677 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/pelicanplatform/pelican
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.0.0-20260408120501-7f73b9c3e677"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-42571
- package https://github.com/PelicanPlatform/pelican
- web https://github.com/PelicanPlatform/pelican/commit/7f73b9c3e677a0ae4a0ec465c5d98bb8bd948854
- web https://github.com/PelicanPlatform/pelican/security/advisories/GHSA-rpfr-x88x-xwcw
- web https://github.com/advisories/GHSA-rpfr-x88x-xwcw