Defined in 2 files
Last patched
challenge_valid in goauthentik/authentik was changed by 1 published CVE fixes in 2026, in 4 distinct patches that added or removed 9 lines in total.
The name occurs in 2 files: authentik/enterprise/stages/authenticator_endpoint_gdtc/stage.py, authentik/enterprise/endpoints/connectors/google_chrome/stage.py.
goauthentik/authentik has 28 CVEs with a located fix in total, so 4% of them touched this function.
Every published CVE whose fix changed challenge_valid, newest first, with the lines each fix touched.
CVE-2026-54730 · authentik/enterprise/endpoints/connectors/google_chrome/stage.py · lines 34–38 · +5 −0
CVE-2026-54730 · authentik/enterprise/stages/authenticator_endpoint_gdtc/stage.py · lines 45–47 · +3 −1
Get an alert when the next CVE fix lands in goauthentik/authentik, with the patched functions.
Monitor authentik CVEsFunctions in the same files that CVE fixes also changed.
Functions in goauthentik/authentik changed by the most CVE fixes.
Common questions about CVE fixes to challenge_valid.
Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.
Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.
