CVE-2026-105301 This candidate was rejected after further investigation determined that it is not a security vulnerability.
Not scored
Published
Updated
Check this codebase for CVE-2026-105301 and fix it if it is affected.
What it is: CVE-2026-105301 is a server-side request forgery vulnerability, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105301 in the wild and no public exploit code.
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-105301/ (Markdown: https://insights.sbomify.com/CVE-2026-105301/index.md)
Attackers can trigger blind SSRF in Keycloak's X.509 authenticator by providing crafted certificates with malicious CRL or OCSP URLs when revocation checking is enabled.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-105301?
CVE-2026-105301 is a server-side request forgery vulnerability, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
This candidate was rejected after further investigation determined that it is not a security vulnerability. The client certificate chain is validated during mTLS negotiation at the TLS layer or reverse proxy before Keycloak processes CRL Distribution Point or OCSP URLs, so only certificates issued by a CA explicitly trusted by the administrator can trigger these requests.
Which versions are affected by CVE-2026-105301?
How do I fix CVE-2026-105301?
No fix has been published for CVE-2026-105301 yet. Limit exposure of the affected software until one is available.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-105301 being exploited?
There is no known exploitation of CVE-2026-105301 in the wild and no public exploit code.
Sources
Also known as GHSA-hg66-m76j-q2rm.