URL Confusion When Scheme Not Supplied in medialize/uri.js

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS

• CVE-2022-1233: 0.80% estimated exploitation activity in the next 30 days; percentile 56.60 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Medialize is a Javascript URL mutation library. When parsing a URL without a scheme and with excessive slashes, like ///www.example.com, URI.js will parse the hostname as null and the path as /www.example.com. Such behaviour is different from that exhibited by browsers, which will parse ///www.example.com as http://www.example.com instead. For example, the following will cause a redirect to http://www.example.com: A fix was released in version 1.19.11.

Published by the source

5 Apr 2022, 00:00 UTC

Last modified by the source

8 Nov 2023, 04:07 UTC

Source last checked

26 Oct 2026, 12:16 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-g694-m8vq-gv9h

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-g694-m8vq-gv9h

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-1233

Advisory: URL Confusion When Scheme Not Supplied in medialize/uri.js
IDs: CVE-2022-1233, GHSA-g694-m8vq-gv9h
Record: https://patchnext.com/advisories/cve-2022-1233 (revision 2, source checked 26 Oct 2026, 12:16 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: urijs 1.19.11. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm urijs: affected < 1.19.11; fixed in 1.19.11

## Suggested inspection (read-only)
- `npm ls urijs --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on urijs.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-g694-m8vq-gv9h (OSV record GHSA-g694-m8vq-gv9h lists affected ranges: npm urijs >=0 <1.19.11 (fixed))
- Verified: https://github.com/advisories/GHSA-g694-m8vq-gv9h (GitHub-reviewed advisory GHSA-g694-m8vq-gv9h lists affected ranges: npm urijs >=0 <1.19.11)

Commands are suggestions: review each one before running it.