Vulnerability in wget (UBUNTU-CVE-2026-15146)

Summary

Vulnerability in wget (UBUNTU-CVE-2026-15146). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.15-1ubuntu1.14.04.5+esm3 or later.

Original description

The description as published by the source.

GNU Wget does not validate the IP address provided by an FTP PASV response while operating in FTP passive mode. A malicious FTP server, or an HTTP server that redirects to an FTP URL, can exploit this behavior to redirect Wget’s data connection to an arbitrary IP address and port. This allows an attacker to forge server-side requests (SSRF) from the machine running Wget, potentially accessing localhost services or internal network resources.

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-15146 has been found in wget.
Risk of unauthorized operations or information disclosure.
What to do: upgrade wget to 1.15-1ubuntu1.14.04.5+esm3 or later.
If unsure, ask your IT team or search "wget UBUNTU-CVE-2026-15146" on the vendor's site.

UBUNTU-CVE-2026-15146 (wget)
Attack vector: local / unauthenticated / no user interaction
Patched: 1.15-1ubuntu1.14.04.5+esm3 — 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 wget.

📍 Affected scope

Check the vendor advisory for the affected versions of wget.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.15-1ubuntu1.14.04.5+esm3.

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

Affected packages

Ubuntu:Pro:14.04:LTS wget

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.15-1ubuntu1.14.04.5+esm3"}]}]

Ubuntu:Pro:16.04:LTS wget

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.17.1-1ubuntu1.5+esm4"}]}]

Ubuntu:Pro:18.04:LTS wget

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.19.4-1ubuntu2.2+esm4"}]}]

Ubuntu:Pro:20.04:LTS wget

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.20.3-1ubuntu2.1+esm3"}]}]

Ubuntu:22.04:LTS wget

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

Ubuntu:24.04:LTS wget

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.21.4-1ubuntu4.4"}]}]

Ubuntu:26.04:LTS wget

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.25.0-2ubuntu4.3"}]}]

References

advisory ubuntu.com
report ubuntu.com
report cve.org
report cgit.git.savannah.gnu.org
report kb.cert.org
report kb.cert.org