← Übersicht Nicht im beobachteten Stack

curl vulnerabilities

USN-8227-1

Ohne Bewertung Unbekannt Kein Fix bekannt

Veröffentlicht
04.05.2026 13:40
Zuletzt geändert
20.05.2026
EPSS (30 Tage)
unbekannt
CVSS-Vektor
keiner

Beschreibung

Originaltext der Quelle, nicht übersetzt.

It was discovered that curl incorrectly reused non-TLS connections when TLS was required in some STARTTLS configurations. A remote attacker could possibly use this issue to obtain sensitive information. (CVE-2026-4873) It was discovered that curl incorrectly reused certain HTTP Negotiate connections. A remote attacker could possibly use this issue to obtain sensitive information. (CVE-2026-5545) It was discovered that curl incorrectly reused certain SMB connections. A remote attacker could possibly use this issue to obtain sensitive information. (CVE-2026-5773) It was discovered that curl could leak proxy credentials when handling redirects in some configurations. A remote attacker could possibly use this issue to obtain sensitive information. (CVE-2026-6253) It was discovered that curl could leak cookies because of stale custom cookie host handling in some requests. A remote attacker could possibly use this issue to obtain sensitive information. (CVE-2026-6276) It was discovered that curl could leak .netrc credentials when reusing proxy connections in some situations. A remote attacker could possibly use this issue to obtain sensitive information. (CVE-2026-6429) It was discovered that curl could leak Digest authentication state when switching proxies in some situations. A remote attacker could possibly use this issue to obtain sensitive information. (CVE-2026-7168)
Weitere betroffene Pakete (4)
Ubuntu:22.04:LTScurl7.81.0-1ubuntu1.24USN-8227-1
Ubuntu:24.04:LTScurl8.5.0-2ubuntu10.9USN-8227-1
Ubuntu:25.10curl8.14.1-2ubuntu1.3USN-8227-1
Ubuntu:26.04:LTScurl8.18.0-1ubuntu2.1USN-8227-1

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Unbekannt) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.