CVE-2026-92289: Software Security Vulnerability Vulnerability

CRITICAL
Advisory Identifier: GHSA-vw4x-93xp-f6f3
Share
CVSS 9.1
CWE-1390
Published
Advisory Summary

CVE-2026-92289 is a CRITICAL (CVSS 9.1) security vulnerability vulnerability (CWE-1390: Weak Authentication) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product uses an authentication mechanism to restrict access to specific users or identities, but the mechanism does not sufficiently prove that the claimed identity is correct.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-92289 at a Glance

CVE Identifier CVE-2026-92289
GHSA Identifier GHSA-vw4x-93xp-f6f3
Severity CRITICAL
CVSS v3.1 Base Score 9.1
CWE Classification CWE-1390: Weak Authentication
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 9.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-92289

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-92289, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-1390: Weak Authentication, where the product uses an authentication mechanism to restrict access to specific users or identities, but the mechanism does not sufficiently prove that the claimed identity is correct. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2026-92289 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-92289
gitlab.ow2.org/lemonldap-ng/lemonl... WEB
https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/releases/v2.23.4
gitlab.ow2.org/lemonldap-ng/lemonl... WEB
https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/work_items/3719
Software Security Information SECURITY
http://www.openwall.com/lists/oss-security/2026/09/25/2

Frequently Asked Questions

What is CVE-2026-92289?
CVE-2026-92289 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-1390: Weak Authentication.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-92289?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-92289?
CVE-2026-92289 has a CVSS v3.1 base score of 9.1 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N.
What CWE is associated with CVE-2026-92289?
CVE-2026-92289 is classified under CWE-1390: Weak Authentication (The product uses an authentication mechanism to restrict access to specific users or identities, but the mechanism does not sufficiently prove that the claimed identity is correct.).
How can I check Maven dependencies for CVE-2026-92289?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-vw4x-93xp-f6f3",
  "modified" : "2026-09-27T00:31:14Z",
  "published" : "2026-09-25T03:31:00Z",
  "aliases" : [ "CVE-2026-92289" ],
  "details" : "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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-92289"
  }, {
    "type" : "WEB",
    "url" : "https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/releases/v2.23.4"
  }, {
    "type" : "WEB",
    "url" : "https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/work_items/3719"
  }, {
    "type" : "WEB",
    "url" : "http://www.openwall.com/lists/oss-security/2026/09/25/2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-1390" ],
    "severity" : "CRITICAL",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-25T01:16:48Z"
  }
}