CVE-2026-15146
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGNU 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.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGNU Wget fails to validate the IP address in FTP PASV responses during passive mode connections. An attacker-controlled FTP server or HTTP-to-FTP redirect can supply a malicious IP in the PASV response, causing Wget to establish its data connection to an arbitrary destination. This enables SSRF attacks from the Wget client toward internal services or private networks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Wget versionRun `wget --version` and note the version number displayed in the first lineAffected if The version is older than the patched version for this vulnerability (any version prior to the fix being applied)
-
Check for passive FTP mode configurationInspect Wget configuration files (~/.wgetrc, /etc/wgetrc) and environment variables for 'passive_ftp=on' or similar settings. Also check if --passive-ftp flag is used in any scripts or cron jobsAffected if Passive FTP mode is explicitly enabled or is the default behavior in the configuration
-
Detect FTP URL usage in automated processesSearch scripts, cron jobs, and configuration files for wget commands containing 'ftp://' URLs: `grep -r 'wget.*ftp://' /path/to/scripts` or `grep -r 'ftp://' /etc/`Affected if Wget is used to fetch from FTP URLs, especially from untrusted or redirecting HTTP sources
-
Check for HTTP-to-FTP redirect handlingReview application logic or scripts that may follow HTTP redirects to FTP servers. Test with `wget -S --spider 'http://example.com/redirect-to-ftp'` if a redirect target is knownAffected if The environment processes HTTP responses that can redirect to FTP URLs, allowing an attacker to supply a malicious PASV IP
You are affected if Wget is installed with a vulnerable version, passive FTP mode is enabled, and the system or application processes FTP URLs from potentially untrusted sources including HTTP-to-FTP redirects.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable passive FTP mode and use active mode with firewall rules, or migrate to SSH/SFTP for file transfers. Avoid processing FTP URLs from untrusted or redirecting HTTP sources.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15146 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-15146 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data