← Back
CVE-2026-40245
Information Disclosure in github.com/free5gc/udr (CVE-2026-40245)
Summary
vulnerability in github.com/free5gc/udr (CVE-2026-40245). Confidential information can be exposed externally. Exploitable via `GET /nudr-dr/v2/application-data/influenceData/subs-to-notify`.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-40245** has been found in github.com/free5gc/udr.
Attackers can target a specific entry point like `GET /nudr-dr/v2/application-data/influenceData/subs-to-notify` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "github.com/free5gc/udr CVE-2026-40245" on the vendor's site.
CVE-2026-40245 (github.com/free5gc/udr) — CWE-200 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /nudr-dr/v2/application-data/influenceData/subs-to-notify / `dnns` / `snssais` / `supis`
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
**information disclosure** (CWE-200) exists in github.com/free5gc/udr. Attackers reach the vulnerable code path via `GET /nudr-dr/v2/application-data/influenceData/subs-to-notify` without authentication.
📍 Affected scope
github.com/free5gc/udr — . Attack surface: GET /nudr-dr/v2/application-data/influenceData/subs-to-notify / `dnns` / `snssais` / `supis`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ 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 `GET /nudr-dr/v2/application-data/influenceData/subs-to-notify` requests with malformed payloads or SQL meta-characters. Run `grep -r 'github.com/free5gc/udr' .` 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/free5gc/udr' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/free5gc/udr` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /nudr-dr/v2/application-data/influenceData/subs-to-notify' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /nudr-dr/v2/application-data/influenceData/subs-to-notify` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
7Post-deployment verification verify
Replay attack against GET /nudr-dr/v2/application-data/influenceData/subs-to-notify on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Go
github.com/free5gc/udr
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"1.4.2"}]}]