Authelia
Open-source authentication and two-factor authorization server.
Authelia patches two access control bypass paths from canonicalization gaps.
◆Recent moves
- 2d ago
v4.39.25
v4.39.25 fixes SMTP handling of IPv6 literal addresses — a narrow bug affecting deployments that route notification emails through IPv6-only SMTP servers. No user-visible impact for the vast majority of setups.
View source ↗ - 3d ago
v4.39.24
v4.39.24 fixes internal test suite output — log color preservation and test group formatting. Pure developer experience, zero user-visible change.
View source ↗ - 4d ago
Five OIDC protocol fixes in v4.39.23
v4.39.23 addresses five distinct OIDC issues: client auth config strategy resolution, client credentials subject foreign key violations, resource indicators grant handling, resource strategy matching, and a storage unbound query. These aren't cosmetic — they affect clients that rely on resource indicators or client credentials grants, both common in enterprise OAuth deployments.
View source ↗ - 9d ago
v4.39.22
v4.39.22 fixes an access token JWT upgrade path in storage. A single targeted fix with no user-visible behavioral change under normal operation.
View source ↗ - 9d ago
Multi-area hardening: LDAP auth, OIDC, and API endpoint fixes in v4.39.21
v4.39.21 is a dense patch release covering LDAP authentication (pooled client handling, stale user aliases, unnecessary read locks), OIDC (configurable rate limits, AMR consistency), and API endpoint gaps. The breadth — fixes across authentication, authorization, configuration, and OIDC in a single release — reflects a backlog flush rather than a single targeted bug.
View source ↗ - 3mo ago
Authelia patches two access control bypass paths: domain miss and LDAP username canonicalization
⚡ SPARKv4.39.20 is a security release fixing two distinct bypass paths: an access control rule domain miss from missing canonicalization, and a username canonicalization gap in Basic Auth with LDAP. Both are authorization failures — not just edge-case behavior — that allowed access to resources the rules should have blocked. The fixes affect any deployment using LDAP and domain-based access control rules.
View source ↗