Vulnerability in github.com/free5gc/nrf (CVE-2026-44325)

Summary

vulnerability in github.com/free5gc/nrf (CVE-2026-44325). Risk of unauthorized operations or information disclosure. Exploitable via `POST /oauth2/token`. Mitigation: upgrade to `1.4.3` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-44325** has been found in github.com/free5gc/nrf. Attackers can target a specific entry point like `POST /oauth2/token` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade github.com/free5gc/nrf to **1.4.3** or later. If unsure, ask your IT team or search "github.com/free5gc/nrf CVE-2026-44325" on the vendor's site.

CVE-2026-44325 (github.com/free5gc/nrf) — CWE-20 / Attack surface: POST /oauth2/token / `models.NrfAccessTokenAccessTokenReq` / `string` / `NrfNfManagementNfType` Patched: `1.4.3` — 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-20) exists in github.com/free5gc/nrf. Attackers reach the vulnerable code path via `POST /oauth2/token` without authentication.

📍 Affected scope

github.com/free5gc/nrf — . Attack surface: POST /oauth2/token / `models.NrfAccessTokenAccessTokenReq` / `string` / `NrfNfManagementNfType`.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure

🔧 How to fix

Update to **1.4.3**.

🛡️ 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 `POST /oauth2/token` requests with malformed payloads or SQL meta-characters. Run `grep -r 'github.com/free5gc/nrf' .` 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

1
Identify exposure identify
```
grep -r 'github.com/free5gc/nrf' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/free5gc/nrf` を grep し、稼働しているサービス・バージョンを把握する。
3
Hunt for indicators of compromise detect
```
grep 'POST /oauth2/token' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'
```
アクセスログで `POST /oauth2/token` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
6
Apply patch patch
```
Upgrade github.com/free5gc/nrf to 1.4.3
```
ステージング環境で 1.4.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Replay attack against POST /oauth2/token on staging to confirm patch closes the vector
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/free5gc/nrf

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.3"}]}]

References

Metadata

CVE: CVE-2026-44325
GHSA: GHSA-f8qv-7x5w-qr48
Published: 2026-05-08
First seen on SecPulse: 22 hours ago
First-seen source: GitHub Security Advisories (Global)

CWE

CWE-20 CWE-755 CWE-843

Detection sources

GitHub Security Advisories (Global) 22 hours ago