CVE-2026-92288 is a weak-authentication flaw in LemonLDAP::NG::Portal for Perl. Versions 2.20.0 through before 2.21.6 and 2.22.0 through before 2.23.4 improperly authenticate requests to the OAuth 2.0 token-introspection endpoint for public Relying Parties. The checkEndPointAuthenticationCredentials() function omits client-secret validation for a Relying Party designated public, but still returns a request-derived authentication method such as client_secret_basic or client_secret_post. Because introspection() rejects requests only when this method is absent or none, an attacker can submit a public client identifier with an arbitrary or empty secret and satisfy the endpoint's authentication check.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An information-disclosure vulnerability in LemonLDAP::NG caused by unauthenticated OAuth 2.0 token introspection.
An information-disclosure vulnerability in LemonLDAP::NG caused by unauthenticated OAuth 2.0 token introspection.
An information-disclosure vulnerability in LemonLDAP::NG that permits unauthenticated OAuth 2.0 token introspection.
An information-disclosure vulnerability in LemonLDAP::NG that permits unauthenticated OAuth 2.0 token introspection.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.