Nixpkgs security tracker

Login with GitHub
⚠️ You are using a production deployment that is still only suitable for demo purposes. Any work done in this might be wiped later without notice.

Suggestion detail

Untriaged
Permalink CVE-2026-55784
7.5 HIGH
  • CVSS version (CVSS): 3.1
  • Attack Vector (AV): Network (N)
  • Attack Complexity (AC): Low (L)
  • Privileges Required (PR): None (N)
  • User Interaction (UI): None (N)
  • Scope (S): Unchanged (U)
  • Confidentiality (C): None (N)
  • Integrity (I): None (N)
  • Availability (A): High (H)
  • Modified Attack Vector (MAV): Network (N)
  • Modified Attack Complexity (MAC): Low (L)
  • Modified Privileges Required (MPR): None (N)
  • Modified User Interaction (MUI): None (N)
  • Modified Confidentiality (MC): None (N)
  • Modified Scope (MS): Unchanged (U)
  • Modified Integrity (MI): None (N)
  • Modified Availability (MA): High (H)
created 1 day, 4 hours ago Activity log
  • Created suggestion
free5GC AUSF authentication contexts can be overwritten by concurrent requests for the same SUPI

free5GC is an open-source implementation of the 5G core network. In version 1.4.4 and earlier, the AUSF component stores per-subscriber authentication state in a global sync.Map named AUSFContext.UePool in internal/context/context.go, keyed only by SUPI. Every request handled by internal/sbi/processor/ue_authentication.go creates an AusfUeContext, and AddAusfUeContextToPool executes ausfContext.UePool.Store(ausfUeContext.Supi, ausfUeContext), unconditionally replacing the active context for that SUPI. An attacker with access to the AUSF SBI/N12 interface can send concurrent POST /nausf-auth/v1/ue-authentications requests for the same target SUPI, causing all attempts to share one logical authentication context URL while K_aut, XRES, and EapID are repeatedly overwritten. A valid EAP-AKA' response for an earlier challenge is then checked against the latest context, causing AT_MAC verification to fail and denying authentication to the selected subscriber while the request flood continues. No fixed version is available as of this review.

Affected products

free5gc
  • ==<= 1.4.4

Matching in nixpkgs

pkgs.free5gc-amf

Open source 5G core network based on 3GPP R15

  • nixos-unstable -
    • nixos-unstable-small 1.4.5

pkgs.free5gc-bsf

Open source 5G core network based on 3GPP R15

  • nixos-unstable -
    • nixos-unstable-small 1.0.4

pkgs.free5gc-chf

Open source 5G core network based on 3GPP R15

  • nixos-unstable -
    • nixos-unstable-small 1.2.5

pkgs.free5gc-nef

Open source 5G core network based on 3GPP R15

  • nixos-unstable -
    • nixos-unstable-small 1.2.5

pkgs.free5gc-nrf

Open source 5G core network based on 3GPP R15

  • nixos-unstable -
    • nixos-unstable-small 1.4.5

pkgs.free5gc-pcf

Open source 5G core network based on 3GPP R15

  • nixos-unstable -
    • nixos-unstable-small 1.4.5

pkgs.free5gc-smf

Open source 5G core network based on 3GPP R15

  • nixos-unstable -
    • nixos-unstable-small 1.4.5

pkgs.free5gc-udm

Open source 5G core network based on 3GPP R15

  • nixos-unstable -
    • nixos-unstable-small 1.4.5

pkgs.free5gc-udr

Open source 5G core network based on 3GPP R15

  • nixos-unstable -
    • nixos-unstable-small 1.4.4

pkgs.free5gc-upf

Open source 5G core network based on 3GPP R15

  • nixos-unstable -

pkgs.free5gc-ausf

Open source 5G core network based on 3GPP R15

  • nixos-unstable -
    • nixos-unstable-small 1.4.5

pkgs.free5gc-nssf

Open source 5G core network based on 3GPP R15

  • nixos-unstable -
    • nixos-unstable-small 1.4.5

pkgs.free5gc-tngf

Open source 5G core network based on 3GPP R15

  • nixos-unstable -
    • nixos-unstable-small 1.1.5

pkgs.free5gc-n3iwf

Open source 5G core network based on 3GPP R15

  • nixos-unstable -
    • nixos-unstable-small 1.3.5

Package maintainers