CVE-2026-25949: Traefik: TCP readTimeout bypass via STARTTLS on Postgres
Traefik is an HTTP reverse proxy and load balancer. Prior to 3.6.8, there is a potential vulnerability in Traefik managing STARTTLS requests. An unauthenticated client can bypass Traefik entrypoint respondingTimeouts.readTimeout by sending the 8-byte Postgres SSLRequest (STARTTLS) prelude and then stalling, causing connections to remain open indefinitely, leading to a denial of service. This vulnerability is fixed in 3.6.8.
Security readout for executives and security teams
Plain-English summary
A remote unauthenticated client can keep vulnerable Traefik connections open indefinitely by abusing STARTTLS handling for Postgres. This can exhaust connection resources and cause service degradation or outage. The issue affects Traefik versions before 3.6.8 and is fixed in 3.6.8.
Executive priority
Prioritize remediation for internet-facing Traefik deployments because the bug can cause outage without authentication. This is not a confidentiality or integrity issue, but availability impact can be material for externally exposed services.
Technical view
Traefik before 3.6.8 can fail to enforce entrypoint respondingTimeouts.readTimeout after a Postgres STARTTLS prelude. A client can stall the connection after the prelude, leaving it open indefinitely. The impact is availability-only denial of service, mapped to CWE-400 and CWE-770 with CVSS 3.1 score 7.5.
Likely exposure
Exposure is most relevant where Traefik versions before 3.6.8 accept network traffic on entrypoints that can receive Postgres STARTTLS-style requests. Internet-facing or broadly reachable Traefik deployments have higher operational risk.
Exploitation context
The source bundle reports unauthenticated network reachability and low attack complexity, but does not cite public exploitation in the wild. KEV status is false, so active exploitation should not be assumed from these sources.
Researcher notes
Evidence supports a STARTTLS handling flaw specific to Traefik connection timeout enforcement. The bundle names the fix release and commit, but does not provide complete downstream product scope beyond Red Hat tracking references. Avoid assuming exploit maturity beyond the stated CVSS and advisory details.
Mitigation direction
Upgrade Traefik to version 3.6.8 or later.
Review Red Hat advisory RHSA-2026:6192 for packaged product guidance.
Restrict network access to affected Traefik entrypoints where feasible.
Monitor Traefik connection counts and resource exhaustion symptoms.
Validation and detection
Inventory Traefik deployments and confirm no instance is below 3.6.8.
Identify entrypoints reachable from untrusted networks.
Check configuration using respondingTimeouts.readTimeout for false assurance.
Review vendor advisories for environment-specific applicability.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.