CVE-2026-114409

NONE
Published: 2026-10-27
Modified: 2026-10-27
Enriched via mock
Tenable Plugin

Checking the public Tenable catalog…

AI Threat Summary

CVE-2026-114409 is a moderate vulnerability affecting the target software. Threat hunters should monitor for exploit attempts and apply vendor patches immediately.

Description

Docker Desktop before version 4.97.0 could write third-party API keys and OAuth access tokens in cleartext to local application logs and diagnostics bundles due to insufficient IPC payload redaction. An attacker with read access to these files could obtain the credentials. These OAuth tokens are not Docker account tokens. Docker Desktop 4.94.0 and 4.95.0 addressed the known logging paths, but logs containing credentials can remain after upgrading. Docker Desktop 4.97.0 fixes the issue and includes cleanup of existing host logs and crash dumps.

Attack Chain
1
Reconnaissance

Attacker scans for vulnerable versions using version banners or PoC scanners

2
Initial Access

Attacker triggers CVE-2026-114409 vulnerability with a crafted request or payload

3
Execution

Vulnerability exploited to perform unauthorized actions on the target system

4
Impact

Depending on vulnerability type, attacker achieves data access, service disruption, or code execution

MITRE ATT&CK Techniques
T1190 Exploit Public-Facing Application
Initial Access

Public-facing application vulnerability exploited for initial access

T1203 Exploitation for Client Execution
Execution

Vulnerability exploited to execute attacker-controlled code

Indicators of Compromise
Type Value Description
user_agent Mozilla/5.0 (compatible; exploit/1.0) Generic exploit scanner user agent pattern
url /api/vuln-endpoint?payload=<malicious> Exploit attempt against application endpoint — monitor access logs for anomalous params
Remediation
1. Apply vendor-supplied security patches immediately. 2. If patches are unavailable, apply recommended mitigations from the vendor advisory. 3. Enable WAF rules or IDS signatures to detect exploitation attempts. 4. Monitor logs for indicators of compromise listed above. 5. Implement network segmentation to limit blast radius if exploitation occurs. 6. Subscribe to vendor security advisories for this product.