VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

uriparser: vulnerability history, versions and safety

uriparser is a package in the Debian ecosystem. Vulert records 18 vulnerabilities for it across 9 releases, from Nov 2018 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
18 vulnerabilities recorded U18
i
6 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
4 in the last 12 months

Most recent disclosure 08 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all uriparser vulnerabilities

Vulert verdict on uriparser i

Updated on 23 Oct 2026

Careful: 6 of the 18 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 18 vulnerabilities on record across 7 years, 4 in the last year.

What to do: Plan around the 6 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 18 over 7 years · 4 in the last year i
  • Latest disclosure 08 May 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 6 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

Every version Vulert holds for uriparser, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 9 of 9 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 6
  • 2019 2
  • 2022 4
  • 2024 2
  • 2025 1
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for uriparser

The 5 most severe of 18 vulnerabilities recorded for this package

Search all 18 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Out-of-Bounds Read Vulnerability in uriparser 9.8 critical 0.9.1-1 16 Jan 2019
Out-of-Bounds Write Vulnerability in uriparser: Critical Risk of Data Corruption 9.8 critical 0.9.0-1 12 Nov 2018
Integer Overflow Vulnerability in uriparser Package 9.8 critical 0.9.0-1 12 Nov 2018
Null Input Vulnerability in uriparser Package - CVE-2018-19200 7.5 high 0.9.0-1 12 Nov 2018
Invalid Free Operations in uriparser - CVE-2021-46141 5.5 medium 0.9.4+dfsg-1+deb11u1 06 Jan 2022

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 uriparser

Is uriparser safe to use?

Vulert records 18 vulnerabilities for uriparser in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 18 not yet rated. 6 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does uriparser have?

18 vulnerabilities are recorded for uriparser in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 18 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new uriparser vulnerabilities disclosed?

4 vulnerabilities were recorded for uriparser in the last 12 months, and the oldest entry in this database dates to 12 Nov 2018. 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 uriparser 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 uriparser for upcoming vulnerabilities?

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