{"api_version":"1","generated_at":"2026-09-25T09:58:59+00:00","cve":"CVE-2026-92289","urls":{"html":"https://cve.report/CVE-2026-92289","api":"https://cve.report/api/cve/CVE-2026-92289.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-92289","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-92289"},"summary":{"title":"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","description":"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.\n\nWith 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.\n\nAn 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.","state":"PUBLISHED","assigner":"CPANSec","published_at":"2026-09-25 01:16:48","updated_at":"2026-09-25 03:16:58"},"problem_types":["CWE-1390","CWE-1390 CWE-1390 Weak Authentication"],"metrics":[],"references":[{"url":"https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/work_items/3719","name":"https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/work_items/3719","refsource":"9b29abf9-4ab0-4765-b253-1875cd9b441e","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/releases/v2.23.4","name":"https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/releases/v2.23.4","refsource":"9b29abf9-4ab0-4765-b253-1875cd9b441e","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"http://www.openwall.com/lists/oss-security/2026/09/25/2","name":"http://www.openwall.com/lists/oss-security/2026/09/25/2","refsource":"af854a3a-2127-422b-91ae-364da2661108","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-92289","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92289","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[{"source":"CNA","title":"","value":"Upgrade to Lemonldap-NG-Portal 2.23.4 or later.","time":"","lang":"en"}],"workarounds":[{"source":"CNA","title":"","value":"For deployments that cannot upgrade to 2.23.4, set RequirePKCE to 1 on public Relying Parties so that a code challenge is always required. Relying Parties created through dynamic registration are always in \"PKCE or secret\" mode, so that endpoint has to be disabled as well.","time":"","lang":"en"}],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"adp":[{"providerMetadata":{"dateUpdated":"2026-09-25T02:10:01.838Z","orgId":"af854a3a-2127-422b-91ae-364da2661108","shortName":"CVE"},"references":[{"url":"http://www.openwall.com/lists/oss-security/2026/09/25/2"}],"title":"CVE Program Container"}],"cna":{"affected":[{"collectionURL":"https://cpan.org/modules","defaultStatus":"unaffected","modules":["Lemonldap::NG::Portal"],"packageName":"Lemonldap-NG-Portal","packageURL":"pkg:cpan/Lemonldap-NG-Portal","programFiles":["lib/Lemonldap/NG/Portal/Lib/OpenIDConnect.pm","lib/Lemonldap/NG/Portal/Issuer/OpenIDConnect.pm"],"programRoutines":[{"name":"Lemonldap::NG::Portal::Lib::OpenIDConnect::checkEndPointAuthenticationCredentials"},{"name":"Lemonldap::NG::Portal::Issuer::OpenIDConnect::token"}],"repo":"https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng","versions":[{"lessThan":"2.23.4","status":"affected","version":"2.23.0","versionType":"custom"}]}],"descriptions":[{"lang":"en","value":"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.\n\nWith 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.\n\nAn 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."}],"problemTypes":[{"descriptions":[{"cweId":"CWE-1390","description":"CWE-1390 Weak Authentication","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-09-25T00:15:49.826Z","orgId":"9b29abf9-4ab0-4765-b253-1875cd9b441e","shortName":"CPANSec"},"references":[{"tags":["issue-tracking"],"url":"https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/work_items/3719"},{"tags":["release-notes"],"url":"https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/releases/v2.23.4"}],"solutions":[{"lang":"en","value":"Upgrade to Lemonldap-NG-Portal 2.23.4 or later."}],"source":{"discovery":"UNKNOWN"},"title":"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","workarounds":[{"lang":"en","value":"For deployments that cannot upgrade to 2.23.4, set RequirePKCE to 1 on public Relying Parties so that a code challenge is always required. Relying Parties created through dynamic registration are always in \"PKCE or secret\" mode, so that endpoint has to be disabled as well."}],"x_generator":{"engine":"cpansec-cna-tool 0.1"}}},"cveMetadata":{"assignerOrgId":"9b29abf9-4ab0-4765-b253-1875cd9b441e","assignerShortName":"CPANSec","cveId":"CVE-2026-92289","datePublished":"2026-09-25T00:15:49.826Z","dateReserved":"2026-09-15T23:43:48.309Z","dateUpdated":"2026-09-25T02:10:01.838Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-25 01:16:48","lastModifiedDate":"2026-09-25 03:16:58","problem_types":["CWE-1390","CWE-1390 CWE-1390 Weak Authentication"],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"92289","Ordinal":"1","Title":"Lemonldap::NG::Portal versions from 2.23.0 before 2.23.4 for Per","CVE":"CVE-2026-92289","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"92289","Ordinal":"1","NoteData":"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.\n\nWith 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.\n\nAn 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.","Type":"Description","Title":"Lemonldap::NG::Portal versions from 2.23.0 before 2.23.4 for Per"}]}}}