<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-08T07:30:46.799832+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cnvd-2026-37846</id>
    <title>cnvd-2026-37846</title>
    <updated>2026-10-08T07:30:46.862075+00:00</updated>
    <content>cnvd-2026-37846</content>
    <link href="https://cve.radiocsirt.org/vuln/cnvd-2026-37846"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-322213</id>
    <title>EUVD-2026-322213</title>
    <updated>2026-10-08T07:30:46.862117+00:00</updated>
    <content>EUVD-2026-322213</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-322213"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-44325</id>
    <title>fkie_cve-2026-44325</title>
    <updated>2026-10-08T07:30:46.862132+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, free5GC's NRF root SBI endpoint POST /oauth2/token contains a parser-level type-confusion bug family. The handler in NFs/nrf/internal/sbi/api_accesstoken.go reflects over models.NrfAccessTokenAccessTokenReq, special-cases only plain string and NrfNfManagementNfType fields, and treats every other field as if it were a single models.PlmnId. The parsed *models.PlmnId is then assigned with reflect.Value.Set() to whichever field name the attacker put in the form body, which panics whenever the destination field's real type is incompatible (slice, different struct, primitive). Gin recovery converts each panic into HTTP 500, but the endpoint remains remotely panicable from a single unauthenticated form-encoded request and is repeatedly triggerable. This vulnerability is fixed in 4.2.2.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-44325"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-f8qv-7x5w-qr48</id>
    <title>GHSA-f8qv-7x5w-qr48 — free5GC NRF: type-confusion panic in POST /oauth2/token structured-form parser via Reflect.Set on incompatible types</title>
    <updated>2026-10-08T07:30:46.862167+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/free5gc/nrf</p>
<p>### Summary
free5GC's NRF root SBI endpoint `POST /oauth2/token` contains a parser-level type-confusion bug family. The handler in `NFs/nrf/internal/sbi/api_accesstoken.go` reflects over `models.NrfAccessTokenAccessTokenReq`, special-cases only plain `string` and `NrfNfManagementNfType` fields, and treats every other field as if it were a single `models.PlmnId`. The parsed `*models.PlmnId` is then assigned with `reflect.Value.Set()` to whichever field name the attacker put in the form body, which panics whenever the destination field's real type is incompatible (slice, different struct, primitive). Gin recovery converts each panic into `HTTP 500`, but the endpoint remains remotely panicable from a single unauthenticated form-encoded request and is repeatedly triggerable across at least 6 confirmed crashing fields.</p>
<p>Note: `/oauth2/token` is unauthenticated by design (it is the OAuth2 token-issuance endpoint). So this is NOT framed as an auth-bypass finding -- it is a parser bug on an intentionally unauthenticated SBI endpoint.</p>
<p>### Details
Validated against the NRF container in the official Docker compose lab.
- Source repo tag: `v4.2.1`
- Running Docker image: `free5gc/nrf:v4.2.1`
- Docker validation date: 2026-03-22
- NRF endpoint: `http://10.100.200.3:8000`</p>
<p>Root cause is in the access-token request parser:
- `NFs/nrf/internal/sbi/api_accesstoken.go:52`
- `NFs/nrf/internal/sbi/api_accesstoken.go:87`
- `NFs/nrf/internal/sbi/api_accesstoken.go:98`
- `NFs/nrf/internal/sbi/api…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-f8qv-7x5w-qr48"/>
  </entry>
</feed>
