CVE-2026-113682 Networknt light-4j 2.1.5 before 2.4.0 Authentication Bypass via Empty LDAP Password
Critical 9.1
Published
Updated
Check this codebase for CVE-2026-113682 and fix it if it is affected.
What it is: CVE-2026-113682 is a critical vulnerability in networknt light-4j, published on 20 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-113682 in the wild and no public exploit code.
Affected product: networknt light-4j. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-113682/ (Markdown: https://insights.sbomify.com/CVE-2026-113682/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-113682?
CVE-2026-113682 is a critical vulnerability in networknt light-4j, published on 20 Oct 2026.
Official description
Networknt light-4j from 2.1.5 before 2.4.0 contains an authentication bypass vulnerability in BasicAuthHandler that allows unauthenticated attackers to log in as LDAP/AD-delegated users. Attackers can send a Basic Authorization header with a known username and empty password, triggering an unauthenticated LDAP bind that is accepted as successful authentication.
Weakness: CWE-287
Which versions are affected by CVE-2026-113682?
How do I fix CVE-2026-113682?
No fix has been published for CVE-2026-113682 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-113682 being exploited?
There is no known exploitation of CVE-2026-113682 in the wild and no public exploit code.
Sources
Also known as GHSA-56rq-859m-p974.