What is the CVSS score of CVE-2026-12566?

CVE-2026-12566 has a CVSS 3.1 base score of 3.1 (Low). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N. EPSS exploitation probability: 0.2%.

Is there a public PoC exploit available for CVE-2026-12566?

Yes, a public proof-of-concept exploit is available for CVE-2026-12566. Prioritise patching immediately. EPSS: 0.2%.

Is there a patch available for CVE-2026-12566?

Yes, a patch is available for CVE-2026-12566. Update the affected software to the latest version immediately.

bbot CVE-2026-12566

EUVD-2026-37814 LOW

Server-Side Request Forgery (SSRF) (CWE-918)

2026-06-17 BLSOPS

GHSA-3mp7-vp6j-2mxx

SSRF Docker Bbot

3.1

CVSS 3.1 · Vendor: BLSOPS

Severity by source

Vendor (BLSOPS) PRIMARY

3.1 LOW

AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N

vuln.today AI

3.1 LOW

MITM network position required (AC:H); attacker needs no credentials (PR:N); impact is solely auth token exfiltration with no integrity or availability consequence.

3.1 AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N

4.0 AV:N/AC:H/AT:N/PR:N/UI:A/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (BLSOPS).

CVSS VectorVendor: BLSOPS

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Lifecycle Timeline

Source Code Evidence Fetched

Jun 17, 2026 - 23:02 vuln.today

Analysis Generated

Jun 17, 2026 - 23:02 vuln.today

DescriptionCVE.org

The docker_pull module uses the realm parameter from a Docker registry's WWW-Authenticate response header as the authentication endpoint without validation. An attacker in a man-in-the-middle position between bbot and a Docker registry could modify this header to redirect the authentication request to an arbitrary endpoint, potentially leaking authentication tokens.

AnalysisAI

Authentication token leakage in Black Lantern Security's bbot docker_pull module exposes Docker credentials to MITM attackers who can substitute the realm parameter in a forged WWW-Authenticate Bearer challenge. When bbot contacts a Docker registry and receives a 401 response, the vulnerable module blindly trusts the attacker-supplied realm URL and forwards authentication material to an arbitrary endpoint outside the legitimate registry domain. No public exploit code has been identified and the vulnerability is not listed in CISA KEV, but an upstream patch commit is available on GitHub.

Technical ContextAI

The Docker Registry HTTP API V2 uses a Bearer token challenge per RFC 6750: on a 401 Unauthorized response, the registry returns a WWW-Authenticate: Bearer header containing realm (the token endpoint URL), service, and scope. The affected bbot component (cpe:2.3:a:black_lantern_security:bbot:*:*:*:*:*:*:*:*) parsed this header with naive string splitting - extracting the realm value verbatim with no domain or scheme validation - then issued an HTTP request to that realm to obtain a Bearer token. CWE-918 (Server-Side Request Forgery) applies here because externally controlled input (the registry HTTP response, interposable by a MITM) directed bbot's outbound authentication request to an unintended destination. The fix in commit c2f4bc0f4 adds _validate_realm(), which compares the registered-domain portion of the realm URL against the original registry URL and rejects any mismatch, including metadata endpoints such as 169.254.169.254.

RemediationAI

Update bbot to the latest available release and verify it includes commit c2f4bc0f4 or later (https://github.com/blacklanternsecurity/bbot/commit/c2f4bc0f4). The fix adds domain-level realm validation that rejects authentication redirects to any endpoint whose registered domain does not match the registry's registered domain. A specific patched version tag was not identified in available data - confirm via git log or package metadata before deploying. If immediate upgrade is not possible, restrict bbot docker_pull scans to registries accessible only over private, controlled network segments (e.g., a dedicated VPN or private VLAN) to eliminate MITM opportunities; note this does not patch the code flaw and should be treated as a temporary compensating control only. Avoid running the docker_pull module over shared, public, or otherwise untrusted network paths until the patch is applied.