CVE-2026-41136: free5gc amf · Expected Behavior Violation
Affects free5gc amfSource CVE Database V5
Public exploit available · CVSS 5.5 Medium : upgrade to 1.4.3 as a priority.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.4.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 21 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade amf and free5gc/amf to 1.4.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| free5gcamf | Affected
| Fixed in
|
GitHubfree5gc/amfpkg:github/free5gc/amfOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade free5GC AMF to version 1.4.3 or later, where this issue is fixed. Patch status is not explicitly confirmed beyond the version fix note; check the vendor advisory for current remediation guidance.
Description
CVE-2026-41136 is a medium severity vulnerability in free5GC AMF versions prior to 1.4.3. The issue arises because the HTTPUEContextTransfer handler lacks a default case for unsupported Content-Type headers, causing deserialization to be skipped silently and the processor to receive an uninitialized request object. This behavior violates expected processing logic and may lead to unexpected application behavior. A fix was introduced in version 1.4.3.