← Back
CVE-2026-46415
high
CVSS 8.2
Vulnerability in pkg.jsn.cam/caddy-defender (CVE-2026-46415)
Summary
vulnerability in pkg.jsn.cam/caddy-defender (CVE-2026-46415). Confidential information can be exposed externally. Exploitable via ``r.RemoteAddr``. Mitigation: upgrade to `0.10.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-46415** has been found in pkg.jsn.cam/caddy-defender.
Attackers can target a specific entry point like ``r.RemoteAddr`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.2/10.
What to do: upgrade pkg.jsn.cam/caddy-defender to **0.10.1** or later.
If unsure, ask your IT team or search "pkg.jsn.cam/caddy-defender CVE-2026-46415" on the vendor's site.
CVE-2026-46415 (pkg.jsn.cam/caddy-defender) — CWE-284 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `r.RemoteAddr` / `RemoteAddr` / `client_ip` / `trusted_proxies`
Patched: `0.10.1` — 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
**A vulnerability** (CWE-284) exists in pkg.jsn.cam/caddy-defender. Attackers reach the vulnerable code path via ``r.RemoteAddr`` without authentication.
📍 Affected scope
pkg.jsn.cam/caddy-defender — . Attack surface: `r.RemoteAddr` / `RemoteAddr` / `client_ip` / `trusted_proxies`.
🔥 Severity
Severity: High (CVSS 8.2/10). Confidential information can be exposed externally
🔧 How to fix
Update to **0.10.1**.
🛡️ 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 'pkg.jsn.cam/caddy-defender' .` 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 'pkg.jsn.cam/caddy-defender' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `pkg.jsn.cam/caddy-defender` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade pkg.jsn.cam/caddy-defender to 0.10.1ステージング環境で 0.10.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
pkg.jsn.cam/caddy-defender
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.10.1"}]}]
References
- package https://github.com/JasonLovesDoggo/caddy-defender
- web https://github.com/JasonLovesDoggo/caddy-defender/security/advisories/GHSA-3h23-rrpc-3p87
- web https://github.com/JasonLovesDoggo/caddy-defender/pull/139
- web https://github.com/advisories/GHSA-3h23-rrpc-3p87
- web [email protected]
- web [email protected]