GHSA-2g9v-7mr5-fgjg — devguard
Fix: l3montree-dev/devguard@6f38310GHSA-2g9v-7mr5-fgjg is a CWE-288 vulnerability in github.com/l3montree-dev/devguard. A fix is available for github.com/l3montree-dev/devguard — see the affected versions and patch details below.
DevGuard has an unauthenticated identity assertion via `X-Admin-Token` header
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-2g9v-7mr5-fgjg.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
github.com/l3montree-dev/devguardReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
The SessionMiddleware accepts a client-supplied X-Admin-Token HTTP request header and uses its raw string value as the authenticated userID when no Kratos session cookie is present. An unauthenticated attacker who knows or can guess a target user's Kratos identity UUID can issue requests as that user. Where the target user is an organisation admin or owner, this gives the attacker full control over that organisation's DevGuard resources.
Patches
The release v1.2.2 patches this issue. Update your DevGuard API Instances to this version.
Workarounds
Configure a reverse proxy to strip the X-Admin-Token header before sending requests to the DevGuard API.
Resources
Fixed commit: https://github.com/l3montree-dev/devguard/commit/6f38310bf93b2a63df3055038f4da82b1f4e6d9a
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/l3montree-dev/devguard | all versions | 1.2.2go get github.com/l3montree-dev/devguard@v1.2.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/l3montree-dev/devguard, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/l3montree-dev/devguard to 1.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2g9v-7mr5-fgjg is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2g9v-7mr5-fgjg can be triaged on real exposure rather than presence alone.
Tailored to GHSA-2g9v-7mr5-fgjg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-2g9v-7mr5-fgjg in your dependencies?
O3 Security finds GHSA-2g9v-7mr5-fgjg across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.