authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
A side-by-side editorial comparison of mod_auth_openidc and Pressable — release velocity, themes, recent moves, and the top alternatives to consider.
mod_auth_openidc keeps hardening its own attack surface, one audited subsystem at a time
This is the Apache module implementing OpenID Connect relying-party support, and its 2.4.20.x line has been an almost unbroken security programme. An internal audit turned up eight issues including an identity-header bypass; PBKDF2 key stretching changed the session encryption key and invalidated every session created by 2.4.19.x and earlier; out-of-bounds reads and writes were fixed in the state-cookie parser. The latest release continues in the same register, hardening file-backed metadata and cache I/O and the shared-memory cache itself.
After a month of bulk tooling, Pressable is hardening what the fleet stores and how sites are named.
Pressable's feed carries titles only — every body is an empty [...] stub, so scope has to be read from headlines. On that basis the last month runs in two phases: a burst of fleet-wide bulk operations through late July, then the AI assistant gaining multi-site collaborator management in early August. The two newest releases move elsewhere: encrypted site environment variables, and flexible site naming with real-time checks.
This is the Apache module implementing OpenID Connect relying-party support, and its 2.4.20.x line has been an almost unbroken security programme. An internal audit turned up eight issues including an identity-header bypass; PBKDF2 key stretching changed the session encryption key and invalidated every session created by 2.4.19.x and earlier; out-of-bounds reads and writes were fixed in the state-cookie parser. The latest release continues in the same register, hardening file-backed metadata and cache I/O and the shared-memory cache itself.
The project is working outward from the code paths an attacker actually reaches: cookie parsing, then session key derivation, then cache storage and the files the module reads at runtime. Keyed hashing of cache keys to stop bucket-chain flooding, refusing non-regular files, capping allocations and writing metadata atomically all address resource-exhaustion and file-substitution classes rather than single bugs. Packaging and commercial distribution notes take up an increasing share of each release body, with Redis and Valkey over TLS behind a commercial agreement.
With the cache and file layers now hardened, the remaining large surface is the HTTP client and provider metadata handling, so that is the likeliest next area — and the 2.4.20.x line should settle into ordinary maintenance once the audit backlog is worked through.
Pressable's feed carries titles only — every body is an empty [...] stub, so scope has to be read from headlines. On that basis the last month runs in two phases: a burst of fleet-wide bulk operations through late July, then the AI assistant gaining multi-site collaborator management in early August. The two newest releases move elsewhere: encrypted site environment variables, and flexible site naming with real-time checks.
The direction is a hosting panel becoming a fleet console, then handing that console to an assistant. Bulk plugin, theme and site operations built the primitives; multi-site collaborator management put privileged access control behind the assistant; global MCP token revocation earlier in the month suggests the agent surface is being given its own credential lifecycle. Encrypted environment variables fit the same maturation — agencies running many sites need per-site secrets that are not in wp-config.
Encrypted environment variables and MCP token revocation both point toward a broader secrets and credential story, so expect environment variables to surface in the AI assistant and the CLI next. The empty feed bodies mean scope cannot be confirmed from this source.
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either mod_auth_openidc or Pressable.
The first patch on 2026.8 is twenty-odd fixes and no new surface.
Alert rate limits stop being per-source and start being per-tenant, by query.
The essay series keeps running ahead of the products it describes.
Both lines patch on the same day, and the reverted JSONata upgrade finally sticks.
The 3.x line finally ships function: authenticated secret writes and render patches.
Folder-level RBAC lands, and approvals finally get a webhook to talk to.
See all mod_auth_openidc alternatives → · See all Pressable alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. mod_auth_openidc and Pressable are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mod_auth_openidc and Pressable are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top mod_auth_openidc alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "mod_auth_openidc alternatives" section above for the current picks, or visit /alternatives/mod-auth-openidc for the full list with editorial commentary on each.
Top Pressable alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Pressable alternatives" section above for the current picks, or visit /alternatives/pressable for the full list with editorial commentary on each.