Servers and applications
GHSA-hmrg-vpp4-gj88
Broken access control in Shared Signals Framework stream management
- Severity
- Medium 5.4
- Published
- 15 Jul 2026
- Last changed
- 15 Jul 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 2026.2.6, 2026.5.5
- Weakness
- Missing authorization (CWE-862)
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Change some data · Slow it down
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L- Sources
- Project advisories (GitHub)
Description
The Shared Signals Framework checked permissions only when a stream was created. The operations that read, change, disable, or delete an existing stream did not, so a low privileged user of an application integrated with a Shared Signals Framework provider could act on that application's event streams without holding the permission required to manage them.
This affects only Enterprise deployments that use the Shared Signals Framework, where a provider is linked to an application as its backchannel provider and that application also issues access tokens to its users. Deployments that do not use the Shared Signals Framework are not affected.
Creating a stream required an explicit permission on the provider, but the operations acting on an existing stream performed no equivalent check. Any user who can sign in to that application could reach these operations and act on the application's streams without holding the stream management permission.
Workarounds
None. Until you can upgrade, we recommend not relying on the Shared Signals Framework for delivery of security events, as a stream's configuration cannot be protected from tampering by users of the linked application on affected versions.
Affected software
| Software | Affected versions |
|---|---|
authentikServers and applications · github:goauthentik/authentik |
|
About authentik
The authentication glue you need.
- Total installations
- 1 millionauthentik
- GitHub stars
- 26,351GitHub, 15 Nov 2026
- Forks
- 2,134GitHub, 15 Nov 2026
- Latest release
- version/2026.8.5GitHub, 15 Nov 2026
- Released
- 21 Oct 2026GitHub
- First published on GitHub
- 30 Dec 2019GitHub
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 2026.8 | 2026.8.5 | Yes |
| 2026.5 | 2026.5.8 | Yes |
| 2026.2 | 2026.2.7 | Ended 18 Aug 2026 |
| 2025.12 | 2025.12.6 | Ended 22 May 2026 |
| 2025.10 | 2025.10.4 | Ended 24 Feb 2026 |
| 2025.8 | 2025.8.6 | Ended 13 Jan 2026 |
From endoflife.date.
Vulnerabilities in authentik
- In our list
- 48
- Published in the last 12 months
- 24
- Critical, last 12 months
- 3
- High, last 12 months
- 17
- Known exploited
- 0
- CVE-2026-94613Denial of Service via Malformed SAML MessagesHigh 7.5 9 Sept 2026
- CVE-2026-94611Certain stored credentials readable with view permission aloneHigh 8.1 9 Sept 2026
- CVE-2026-94612Authentication bypass in SAML Sources via assertion confusion and replayHigh 7.4 9 Sept 2026
- CVE-2026-94609Privilege escalation via delegated group and user managementHigh 8.8 9 Sept 2026
- CVE-2026-94606MFA bypass via recipient override in the email authenticatorHigh 8.9 9 Sept 2026
- CVE-2026-61574RAC endpoints and their stored credentials are exposed to any authenticated user, and connections can cross application boundariesHigh 8.8 15 Jul 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-hmrg-vpp4-gj88
- github.com https://github.com/goauthentik/authentik/security/advisories/GHSA-hmrg-vpp4-gj88