Bug 2540977

Summary:	CVE-2026-92289 lemonldap-ng: lemonldap-ng: Authentication bypass via improper PKCE verification [epel-all]
Product:	[Fedora] Fedora EPEL	Reporter:	Vladimir Vasilev <vvasilev>
Component:	lemonldap-ng	Assignee:	Xavier Bachelot <xavier>
Status:	ON_QA ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	epel10	CC:	xavier
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	{"flaws": ["6c06cc95-24d3-448a-b318-62d62d786043"]}
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2540882

Description Vladimir Vasilev 2026-09-25 07:34:42 UTC

Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

Lemonldap::NG::Portal versions from 2.23.0 before 2.23.4 for Perl allow a PKCE bypass for public Relying Parties in "PKCE or secret" mode because checkEndPointAuthenticationCredentials does not verify the client secret.

With oidcRPMetaDataOptionsRequirePKCE set to 2, the authorization endpoint issues a code even when the request carries no code_challenge, and token() admits the exchange as long as a challenge was stored or an authentication method was returned for the caller. checkEndPointAuthenticationCredentials() skips the secret comparison for a Relying Party marked public and still returns the method deduced from the request, so any Basic or form credential satisfies the secret branch. validatePKCEChallenge() then passes, because neither a challenge nor a verifier is present.

An attacker who intercepts an authorization code issued to a public Relying Party can exchange it for the user's access, ID and refresh tokens by replaying the client_id with an arbitrary secret, which is the attack PKCE prevents. Dynamic client registration creates every Relying Party in this mode.

Comment 1 Fedora Update System 2026-09-25 08:15:23 UTC

FEDORA-EPEL-2026-d54ae88fef (lemonldap-ng-2.23.4-1.el10_2) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-d54ae88fef

Comment 2 Fedora Update System 2026-09-25 08:15:30 UTC

FEDORA-EPEL-2026-306ffcea82 (lemonldap-ng-2.23.4-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-306ffcea82

Comment 3 Fedora Update System 2026-09-25 08:15:34 UTC

FEDORA-EPEL-2026-d6a23de049 (lemonldap-ng-2.23.4-1.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-d6a23de049

Comment 4 Fedora Update System 2026-09-25 08:15:39 UTC

FEDORA-EPEL-2026-3ddfd6e04f (lemonldap-ng-2.23.4-1.el10_4) has been submitted as an update to Fedora EPEL 10.4.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-3ddfd6e04f

Comment 5 Fedora Update System 2026-09-25 08:15:44 UTC

FEDORA-EPEL-2026-1b43c541cb (lemonldap-ng-2.23.4-1.el10_3) has been submitted as an update to Fedora EPEL 10.3.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-1b43c541cb

Comment 6 Fedora Update System 2026-09-26 02:01:14 UTC

FEDORA-EPEL-2026-306ffcea82 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-306ffcea82

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2026-09-26 02:14:44 UTC

FEDORA-EPEL-2026-3ddfd6e04f has been pushed to the Fedora EPEL 10.4 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-3ddfd6e04f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2026-09-26 02:17:43 UTC

FEDORA-EPEL-2026-1b43c541cb has been pushed to the Fedora EPEL 10.3 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-1b43c541cb

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2026-09-26 02:20:45 UTC

FEDORA-EPEL-2026-d54ae88fef has been pushed to the Fedora EPEL 10.2 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-d54ae88fef

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2026-09-26 02:23:34 UTC

FEDORA-EPEL-2026-d6a23de049 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-d6a23de049

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.