Vulnerability in github.com/l3montree-dev/devguard (CVE-2026-42300)
Summary
Vulnerability in github.com/l3montree-dev/devguard (CVE-2026-42300). Risk of unauthorized operations or information disclosure. Exploitable via SessionMiddleware. Mitigation: upgrade to 1.2.2 or later.
Original description
The description as published by the source.
DevGuard provides vulnerability management for the full software supply chain. Prior to 1.2.2, 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. This vulnerability is fixed in 1.2.2.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-42300 has been found in github.com/l3montree-dev/devguard.
Attackers can target a specific entry point like SessionMiddleware over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/l3montree-dev/devguard to 1.2.2 or later.
If unsure, ask your IT team or search "github.com/l3montree-dev/devguard CVE-2026-42300" on the vendor's site.
CVE-2026-42300 (github.com/l3montree-dev/devguard) — CWE-288
Attack surface: SessionMiddleware / userID / admin / owner
Patched: 1.2.2 — apply immediately
Workaround: Configure a reverse proxy to strip the X-Admin-Token header before sending requests to the DevGuard API.
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.
A vulnerability (CWE-288) exists in github.com/l3montree-dev/devguard. Attackers reach the vulnerable code path via SessionMiddleware.
Check the vendor advisory for the affected versions of github.com/l3montree-dev/devguard. Attack surface: SessionMiddleware / userID / admin / owner.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.2.2.
Workaround: Configure a reverse proxy to strip the X-Admin-Token header before sending requests to the DevGuard API.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/l3montree-dev/devguard' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/l3montree-dev/devguard' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/l3montree-dev/devguardを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Configure a reverse proxy to strip the `X-Admin-Token` header before sending requests to the DevGuard API.パッチが適用されるまでの応急処置として、Configure a reverse proxy to strip the
X-Admin-Tokenheader before sending requests to the DevGuard API. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade github.com/l3montree-dev/devguard to 1.2.2ステージング環境で 1.2.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com