How severe is CVE-2023-36617?

CVE-2023-36617 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2023-36617?

CVE-2023-36617 affects the following packages: uri (RubyGems), uri (RubyGems), uri (RubyGems), uri (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2023-36617?

Update uri to 0.10.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-36617 is resolved across your whole dependency graph.

How do I detect CVE-2023-36617 in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for uri, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-36617 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2023-36617 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-36617 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-36617?

CVE-2023-36617 has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 77th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-36617?

CVE-2023-36617 is classified as CWE-1333 (CWE-1333). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-36617 published, and has it been updated?

CVE-2023-36617 was published on June 29, 2023 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎

💎 RubyGems

Not in CISA KEV

MEDIUM severity

CVE-2023-36617 — uri

MEDIUMFix: ruby/uri@05b1e7d

CVE-2023-36617 is a medium-severity (CVSS 5.3) CWE-1333 vulnerability in uri. A fix is available for uri — see the affected versions and patch details below.

URI gem has ReDoS vulnerability

Also known asGHSA-hww2-5g85-429m

Published

Jun 29, 2023

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs77th percentile — riskier than 77% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

💎uri💎uri💎uri💎uri

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

NOTE: this issue exists becuse of an incomplete fix for CVE-2023-28755. Version 0.10.3 is also a fixed version.

The Ruby advisory recommends updating the uri gem to 0.12.2. In order to ensure compatibility with the bundled version in older Ruby series, you may update as follows instead:

For Ruby 3.0: Update to uri 0.10.3
For Ruby 3.1 and 3.2: Update to uri 0.12.2.

You can use gem update uri to update it. If you are using bundler, please add gem uri, >= 0.12.2 (or other version mentioned above) to your Gemfile.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`uri`	≥ 0.10.1&&< 0.10.3	0.10.3`bundle update uri --conservative`
💎RubyGems	`uri`	≥ 0.12.0&&< 0.12.2	0.12.2`bundle update uri --conservative`
💎RubyGems	`uri`	≥ 0.11.0&&< 0.11.2	0.11.2`bundle update uri --conservative`
💎RubyGems	`uri`	all versions	0.10.0.3`bundle update uri --conservative`

Affected Products

1 product · 2 configurations

Application

uriruby-lang

≥ 0.11.0 && < 0.12.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for uri, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update uri to 0.10.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-36617 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This vulnerability exists due to an incomplete fix for CVE-2023-28755 in upstream.

Product	Fixed in	Advisory
Red Hat Enterprise Linux 8	`ruby:3.1-8090020240311122605.a75119d5`	RHSA-2024:1431
Red Hat Enterprise Linux 8	`ruby:2.5-8100020240627152904.489197e6`	RHSA-2024:4499
Red Hat Enterprise Linux 9	`ruby:3.1-9030020240320163942.9`	RHSA-2024:1576

Frequently Asked Questions

A ReDoS issue was discovered in the URI component before 0.12.2 for Ruby. The URI parser mishandles invalid URLs that have specific characters. There is an increase in execution time for parsing strings to URI objects with `rfc2396_parser.rb` and `rfc3986_parser.rb`. NOTE: this issue exists becuse of an incomplete fix for CVE-2023-28755. Version 0.10.3 is also a fixed version. [The Ruby advisory recommends](https://www.ruby-lang.org/en/news/2023/06/29/redos-in-uri-CVE-2023-36617/) updating the uri gem to 0.12.2. In order to ensure compatibility with the bundled version in older Ruby series,

O3 Security · Impact-Aware SCA

Is CVE-2023-36617 in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works