Skip to main content

Docker CVE-2026-92543

| EUVDEUVD-2026-94484 HIGH
Improper Certificate Validation (CWE-295)
N/A vendor:alpine
7.6
CVSS 4.0 · Vendor: vendor:alpine
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain man-in-the-middle network position
  2. Delivery
    Intercept client TLS connection
  3. Exploit
    Present forged certificate accepted due to improper validation
  4. Execution
    Decrypt/tamper with session traffic
  5. Impact
    Disclose or alter sensitive data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V12 - Secure Communication Certificate validation
Exploitation Conditions

Exploitation requires the attacker to occupy a man-in-the-middle position on the network path (reflected by AT:P, attack requirement present) and requires the victim to initiate a TLS connection with the vulnerable Docker/moby client (UI:P, passive user interaction). The improper certificate validation (CWE-295) means a forged or invalid certificate is accepted, so the attacker must be able to intercept and respond on the TLS channel. Limiting factors: high attack complexity (AC:H), dependence on achieving a privileged network position, and the need for a user/client to establish the affected connection - exploitation is not possible by simply reaching the host remotely. Affected: Alpine Linux docker package before 29.8.2-r0.

Impact

CVSS 4.0 rates this 7.6 (High), driven by high confidentiality and integrity impact (VC:H/VI:H) over a network vector with no privileges required (AV:N/PR:N). However, the real-world exploitation signals temper this: AC:H (high attack complexity), AT:P (a specific attack requirement/precondition must be present), and UI:P (passive user interaction) all indicate exploitation is non-trivial and situational rather than trivially remote. This aligns with CWE-295 (Improper Certificate Validation), which typically requires the attacker to hold a man-in-the-middle position on the network path. No EPSS score, KEV listing, or POC is present in the supplied data, so there is no public exploit identified at time of analysis and no evidence of active exploitation. Net assessment: a genuinely impactful flaw in a very widely deployed product, but the combination of required MITM positioning, high complexity, and user interaction makes it a patch-in-normal-cycle item rather than an emergency, absent any exploitation signal. Note the input provides only a CVSS 4.0 vector (no 3.1), and the description ('docker fixed in 29.8.2-r0') contains no technical detail - the CWE and advisory reference, not the description, drive this interpretation; verify specifics against moby advisory GHSA-7cfq-22r6-qp73.

Exploit ScenarioDerived

An attacker positioned on the network path between a Docker/moby client and a remote TLS endpoint (e.g. a registry or daemon connection) exploits improper certificate validation to present a fraudulent certificate that the client accepts. This lets the attacker intercept or tamper with the TLS session, disclosing sensitive data (such as credentials or image content) and potentially altering transferred data. No public exploit code is identified at time of analysis, and success requires both the MITM position and the victim initiating a connection.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv2 – Oct 07, 2026

Improper TLS certificate validation in the Docker client shipped as the Alpine Linux docker package before 29.8.2-r0 allows an attacker who already occupies a man-in-the-middle position on the network path to impersonate a legitimate registry or daemon endpoint and have forged or otherwise invalid certificates accepted. Successful exploitation requires the victim to initiate the affected TLS connection (passive user interaction), but grants high confidentiality and integrity impact over the redirected traffic, since the client trusts the attacker-supplied certificate instead of rejecting it. No public exploit code or confirmed active exploitation was identified at time of analysis, and the fix is a package update to docker 29.8.2-r0.

Earlier versions of this analysis (1)
v1 Sep 30, 2026 - 22:10

The Alpine Linux docker package is fixed in version 29.8.2-r0, resolving CVE-2026-92543 for users who installed Docker from Alpine's repositories. The advisory is a package-tracker fix notice only: no CVSS score, CVSS vector, or CWE was published, so the flaw's nature (container escape, privilege escalation, information disclosure, denial of service, or something else) and the required attacker prerequisites are not characterized in the available data. No public exploit code was identified at time of analysis, and no CISA KEV listing exists; administrators running Alpine's docker package below 29.8.2-r0 should upgrade and consult the upstream Docker/Moby advisory for the full technical details.

RemediationAI

The primary fix is the vendor-released Docker package update to version 29.8.2-r0 on Alpine Linux; apply it with 'apk update && apk upgrade docker' (or upgrade the full base image/system) and then restart the Docker daemon and any long-running clients so the patched TLS verification code is loaded. Because the flaw only manifests when a client connects over TLS to an endpoint that an attacker can intercept, interim compensating controls are to avoid running affected Docker clients across untrusted networks (public Wi-Fi, shared hosting networks, or any path not under your administrative control) and to force all daemon and registry communication through an authenticated, encrypted tunnel you control, such as a VPN or SSH port-forward, which denies the attacker the required man-in-the-middle position at the cost of added connection setup and reduced flexibility for remote clients. Pinning registries and daemons to endpoints reachable only over trusted internal segments and reviewing logs for unexpected certificate rejection handling can reduce exposure while upgrades roll out. Consult the upstream advisory at https://github.com/moby/moby/security/advisories/GHSA-7cfq-22r6-qp73 for the exact upstream fix version and any additional guidance for non-Alpine builds, and note that updating only the client binary without restarting dependent processes will leave the vulnerable code path in memory.

Affected VersionsENISA

Docker Engine 0 <29.8.2
moby 0 <v2.0.0-beta.25

Affected Packages

euvd docker_engine fix: 29.8.2

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-295 (Improper Certificate Validation), a flaw in the TLS trust-handling logic of the Docker client (moby), as packaged and distributed by Alpine Linux. When the client establishes a TLS session, it must verify the server certificate chain against its configured trust anchors and reject certificates that are expired, self-signed, hostname-mismatched, or signed by an untrusted CA; a failure in that verification path means an adversary sitting on the network path can present a forged certificate and terminate or relay the TLS session without the client noticing. The assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N) reflects that the attack is network-reachable and requires no credentials (PR:N), but is gated by two conditions: a privileged network position (AT:P in the CVSS 4.0 form, mapped as high attack complexity in 3.1) and a user or client initiating the connection (UI:P / UI:R). Confidentiality and integrity are both rated High because intercepted Docker client traffic can expose images, registry credentials, and API payloads and can be modified in transit; availability is unaffected. The only reference provided is the upstream GitHub Security Advisory GHSA-7cfq-22r6-qp73, and the Alpine tracker entry identifies this as the docker fix rolled into release 29.8.2-r0.

Know when Alpine gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (vendor:alpine) PRIMARY 7.6 HIGH
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
vuln.today AI 6.8 MEDIUM

MITM position and client-initiated TLS connection justify AC:H and UI:R; no auth needed (PR:N); cert-validation flaw exposes and allows tampering of data (C:H/I:H), no availability impact.

3.1 AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
4.0 AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (vendor:alpine).

CVSS VectorVendor: vendor:alpine

Attack Vector
Network
Attack Complexity
High
Attack Requirements
Present
Privileges Required
None
User Interaction
Passive
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

3
Patch available
Oct 07, 2026 - 18:02 EUVD
CVSS changed
Oct 07, 2026 - 17:22 NVD
7.6 (HIGH)
CVE Published
Sep 30, 2026 - 22:10 cve.org
MEDIUM

DescriptionCVE.org

Alpine Linux: docker fixed in 29.8.2-r0

Executive ViewAI

Why It Matters

Alpine Linux's Docker client package (versions before 29.8.2-r0) has a high-severity TLS certificate validation flaw that could allow a network man-in-the-middle to impersonate container registries or daemon endpoints, risking confidentiality and integrity of container images and orchestration traffic. Organizations using Alpine-based Docker clients in untrusted or shared network environments are most exposed, and leadership should care because successful exploitation could enable supply-chain tampering or credential theft. No public exploit identified at time of analysis, but the vulnerability is rated high severity.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.1%
Top 100% exploitable
Prevalence
High
Docker/moby container engine is widely deployed across enterprise and cloud environments
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy