Vulnerability in curl (UBUNTU-CVE-2026-12064)

Summary

Vulnerability in curl (UBUNTU-CVE-2026-12064). Data can be tampered with by attackers. Mitigation: upgrade to 8.14.1-2ubuntu1.5 or later.

Original description

The description as published by the source.

When a user invokes curl using a schemeless URL combined with --proto-default sftp (or scp), a disconnect occurs between the tool layer and libcurl. The tool layer incorrectly infers the URL scheme, which erroneously bypasses the initialization of critical SSH security options like CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256 and CURLOPT_SSH_KNOWNHOSTS. Conversely, the libcurl runtime successfully honors CURLOPT_DEFAULT_PROTOCOL and establishes the connection via SFTP/SCP as specified. Because the tool layer skipped the security configuration, these SSH host verification options are silently omitted, causing curl to connect to an unverified SSH remote host without throwing an error.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as UBUNTU-CVE-2026-12064 has been found in curl.
Data can be tampered with by attackers.
What to do: upgrade curl to 8.14.1-2ubuntu1.5 or later.
If unsure, ask your IT team or search "curl UBUNTU-CVE-2026-12064" on the vendor's site.

UBUNTU-CVE-2026-12064 (curl)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 8.14.1-2ubuntu1.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in curl.

📍 Affected scope

Check the vendor advisory for the affected versions of curl.

🔥 Severity

Severity: ?. Data can be tampered with by attackers.

🔧 How to fix

Update to 8.14.1-2ubuntu1.5.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'curl' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'curl' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で curl を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade curl to 8.14.1-2ubuntu1.5
```
ステージング環境で 8.14.1-2ubuntu1.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Ubuntu:25.10 curl

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.14.1-2ubuntu1.5"}]}]

Ubuntu:26.04:LTS curl

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.18.0-1ubuntu2.3"}]}]

References

advisory ubuntu.com
report ubuntu.com
report cve.org
report curl.se