How many CVEs have patched _get_name_id?

2 published CVEs changed _get_name_id in goauthentik/authentik, in 5 distinct patches totalling 9 changed lines, between 2026 and 2026.

What is the latest CVE that changed _get_name_id?

CVE-2026-57580 (authentik: Account Takeover via SAML NameID Comment Truncation), published 2026-08-18, changed lines 297 of authentik/sources/saml/processors/response.py.

How does _get_name_id compare to the rest of goauthentik/authentik?

goauthentik/authentik has 28 CVEs with a located fix in total; 2 of them changed _get_name_id.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

goauthentik/authentik

Function

_get_name_id

Name: _get_name_id in goauthentik/authentik: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

authentik/sources/saml/processors/response.py

Last patched August 18, 2026

2

CVEs

That changed this function

5

Distinct patches

Backports counted once

9

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

_get_name_id in goauthentik/authentik was changed by 2 published CVE fixes in 2026, in 5 distinct patches that added or removed 9 lines in total.

goauthentik/authentik has 28 CVEs with a located fix in total, so 7% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed _get_name_id, newest first, with the lines each fix touched.

authentik: Account Takeover via SAML NameID Comment Truncation
CVE-2026-57580 · line 297 · +1 −1
Critical · CVSS 9.4
EPSS 0.6%2026-08-18
authentik: SAML NameID XML Comment Injection Enables Authentication Bypass via Identifier Truncation
CVE-2026-40165 · lines 272–287 · +3 −4 in 2 hunks
High · CVSS 8.7
EPSS 0.7%2026-05-20

Get an alert when the next CVE fix lands in goauthentik/authentik, with the patched functions.

Monitor authentik CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in goauthentik/authentik changed by the most CVE fixes.

__post_init_code3 CVEs · authentik/providers/oauth2/views/token.py parse2 CVEs · authentik/sources/saml/processors/response.py NewWebServer2 CVEs · internal/web/web.go send1 CVEs · web/src/admin/stages/authenticator_sms/AuthenticatorSMSStageForm.ts validate_users1 CVEs · authentik/core/api/groups.py validate_groups1 CVEs · authentik/core/api/users.py

All patched functions in goauthentik/authentik

Frequently asked questions

Common questions about CVE fixes to _get_name_id.

How many CVEs have patched _get_name_id?: 2 published CVEs changed _get_name_id in goauthentik/authentik, in 5 distinct patches totalling 9 changed lines, between 2026 and 2026.
What is the latest CVE that changed _get_name_id?: CVE-2026-57580 (authentik: Account Takeover via SAML NameID Comment Truncation), published 2026-08-18, changed lines 297 of authentik/sources/saml/processors/response.py.
How does _get_name_id compare to the rest of goauthentik/authentik?: goauthentik/authentik has 28 CVEs with a located fix in total; 2 of them changed _get_name_id.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track goauthentik/authentik CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing