Bug 2540974

Summary: CVE-2026-92288 lemonldap-ng: lemonldap-ng: Information disclosure via unauthenticated OAuth 2.0 token introspection [epel-all]
Product: [Fedora] Fedora EPEL Reporter: Vladimir Vasilev <vvasilev>
Component: lemonldap-ngAssignee: Xavier Bachelot <xavier>
Status: ON_QA --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: epel10CC: xavier
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: {"flaws": ["90c8dcec-733d-4c27-b598-0d4e880e14f0"]}
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: 2540880    

Description Vladimir Vasilev 2026-09-25 07:34:17 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.20.0 before 2.21.6, from 2.22.0 before 2.23.4 for Perl allow unauthenticated OAuth2 token introspection because checkEndPointAuthenticationCredentials does not verify the client secret of a public Relying Party.

checkEndPointAuthenticationCredentials() skips the secret comparison for a Relying Party marked public and still returns the authentication method deduced from the request, client_secret_basic or client_secret_post. introspection() rejects a caller only when that method is missing or none, so a request carrying a public client_id and an arbitrary or empty secret passes the endpoint's authentication check.

An attacker who holds an access token and knows the client_id of any public Relying Party can confirm the token is active and read its metadata, including scope, audience, expiry and the sub claim. The sub claim is computed with the calling Relying Party's user identifier attribute, so an attacker can translate a user identifier from one Relying Party to another, defeating per-client and pseudonymous identifiers.

Comment 1 Fedora Update System 2026-09-25 08:15:21 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:22 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:22 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 4 Fedora Update System 2026-09-25 08:15:22 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 5 Fedora Update System 2026-09-25 08:15:23 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 6 Fedora Update System 2026-09-26 02:01:12 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:43 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:41 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:44 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:32 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.