VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

wget2: vulnerability history, versions and safety

wget2 is a package in the OSS-Fuzz ecosystem. Vulert records 6 vulnerabilities for it across 3 affected ranges, from Jul 2020 to Jan 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded H2 M4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all wget2 vulnerabilities

Vulert verdict on wget2 i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 13 Jan 2021. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 6 vulnerabilities on record across 1 year, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 6 over 1 year · 0 in the last year i
  • Latest disclosure 13 Jan 2021 i
  • Highest CVSS n/a i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
from 8df8100af928f0377ee79a3886f4929fca9fb206 up to 6e5c820cf7a1d54b7732af3c6a3c9727d4bd78bf (exclusive) 4
from 59d9ecd9c0a9411c9b02185e49637396a77bd205 up to e225d9109cabbd25a063500c129ef8c47a763d19 (exclusive) 1
from 756e470de942ec830a9a424a2340b7e986e9fe7c up to f6e762181df35bb081d8e776df6cbb6af4bd5939 (exclusive) 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 5
  • 2021 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 6 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for wget2

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-buffer-overflow in set_char_prefix in wget2 N/A high f6e762181df35bb081d8e776df6cbb6af4bd5939 13 Jan 2021
Heap-use-after-free in rpl_glob in wget2 N/A high e225d9109cabbd25a063500c129ef8c47a763d19 22 Jul 2020
Heap-buffer-overflow in _iri_unescape_inline in wget2 N/A medium 6e5c820cf7a1d54b7732af3c6a3c9727d4bd78bf 01 Jul 2020
Heap-buffer-overflow in _iri_unescape_inline in wget2 N/A medium 6e5c820cf7a1d54b7732af3c6a3c9727d4bd78bf 01 Jul 2020
Heap-buffer-overflow in _iri_unescape_inline in wget2 N/A medium 6e5c820cf7a1d54b7732af3c6a3c9727d4bd78bf 01 Jul 2020

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About wget2

Is wget2 safe to use?

Vulert records 6 vulnerabilities for wget2 in OSS-Fuzz: 0 critical, 2 high, 4 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does wget2 have?

6 vulnerabilities are recorded for wget2 in the OSS-Fuzz ecosystem: 0 critical, 2 high, 4 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new wget2 vulnerabilities disclosed?

0 vulnerabilities were recorded for wget2 in the last 12 months, and the oldest entry in this database dates to 01 Jul 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of wget2 are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor wget2 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the wget2 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.