CVE-2026-4519

LOWNVD 3.33.3—
EchelonGraph scoreMEDIUM confidence

Score 3.3 from GitHub Security Advisory published 2026-03-20. NVD baseline CVSS 3.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 3.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The webbrowser.open() API would accept leading dashes in the URL which could be handled as command line options for certain web browsers. New behavior rejects leading dashes. Users are recommended to sanitize URLs prior to passing to webbrowser.open().

CVSS v3
3.3
EG Score
3.3LOWmedium confidence
EG Risk
15
EG Risk 15/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity33% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

Published

March 20, 2026

Last Modified

August 13, 2026

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhaiis/model-opt-cuda-rhel9:17806819842026-06-10redhat
redhatrhui5/rhua-rhel9:17797982222026-05-27redhat
redhatrhaiis/vllm-cuda-rhel9:17792236542026-05-20redhat
redhatrhaiis/vllm-rocm-rhel9:17792236512026-05-20redhat
redhatpython3.14-0:3.14.4-2.el10_22026-05-19redhat
redhatpython3.12-0:3.12.13-2.el10_22026-05-19redhat
redhatpython3.14-0:3.14.4-2.el9_82026-05-19redhat
redhatpython3.9-0:3.9.25-7.el9_82026-05-19redhat
redhatpython3.12-0:3.12.13-2.el9_82026-05-19redhat
redhatpython3.11-0:3.11.13-9.el9_82026-05-19redhat
redhatrhaiis/vllm-spyre-rhel9:17782445462026-05-12redhat
redhatrhaiis/model-opt-cuda-rhel9:17782445592026-05-11redhat
redhatrhaiis/vllm-rocm-rhel9:17782445312026-05-11redhat
redhatrhaiis/vllm-cuda-rhel9:17782746662026-05-11redhat
redhatrhpam-7/rhpam-smartrouter-rhel8:7.13.5-4.17773257082026-05-05redhat
redhatpython3.9-0:3.9.18-3.el9_4.122026-04-23redhat
redhatpython3.12-0:3.12.1-4.el9_4.122026-04-23redhat
redhatpython-0:2.6.6-70.el6_10.32026-04-23redhat
redhatrhui5/rhua-rhel9:17768688422026-04-23redhat
redhatrhelai3/disk-image-cuda-rhel9:17769388712026-04-23redhat
redhatrhelai3/bootc-rocm-rhel9:17767735052026-04-23redhat
redhatpython3.11-0:3.11.2-2.el8_8.92026-04-22redhat
redhatpython3-0:3.6.8-21.el7_9.52026-04-22redhat
redhatpython-0:2.7.5-94.el7_9.42026-04-22redhat
redhatpython3.11-0:3.11.11-2.el9_6.62026-04-22redhat
redhatpython3-0:3.6.8-39.el8_4.102026-04-22redhat
redhatpython3-0:3.6.8-51.el8_8.142026-04-21redhat
redhatpython3.11-0:3.11.2-2.el9_2.112026-04-21redhat
redhatpython3.9-0:3.9.10-4.el9_0.102026-04-21redhat
redhatpython3.9-0:3.9.21-2.el9_6.52026-04-21redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(17 across 7 ecosystems)
Debian:11(4)
PackageVulnerable rangeFix by version rangeDependents
jython2.7.2+repack1-3, 2.7.2+repack1-4, 2.7.2+repack1-5, 2.7.3+repack1-1
  • every version on: no fix on record
—
pypy37.3.10+dfsg-1 ... 7.3.9+dfsg-5 (53 versions)
  • every version on: no fix on record
—
python2.72.7.18-10 ... 2.7.18-9 (10 versions)
  • every version on: no fix on record
—
python3.93.9.2-1 ... 3.9.2-1+deb11u6 (7 versions)
  • every version up to 3.9.2-1+deb11u7: fixed in 3.9.2-1+deb11u7
—
Debian:14(4)
PackageVulnerable rangeFix by version rangeDependents
jython2.7.3+repack1-1
  • every version on: no fix on record
—
pypy37.3.19+dfsg-2 ... 7.3.21+dfsg-4 (9 versions)
  • every version up to 7.3.22+dfsg-1: fixed in 7.3.22+dfsg-1
—
python3.133.13.11-1 ... 3.13.9-1 (7 versions)
  • every version up to 3.13.14-1: fixed in 3.13.14-1
—
python3.143.14.0-1 ... 3.14.3-5 (19 versions)
  • every version up to 3.14.4-1: fixed in 3.14.4-1
—
Debian:12(3)
PackageVulnerable rangeFix by version rangeDependents
jython2.7.3+repack1-1
  • every version on: no fix on record
—
pypy37.3.11+dfsg-2 ... 8.0.0+dfsg-1 (31 versions)
  • every version on: no fix on record
—
python3.113.11.2-6 ... 3.11.2-6+deb12u7 (8 versions)
  • every version up to 3.11.2-6+deb12u8: fixed in 3.11.2-6+deb12u8
—
Debian:13(3)
PackageVulnerable rangeFix by version rangeDependents
jython2.7.3+repack1-1
  • every version on: no fix on record
—
pypy37.3.19+dfsg-2 ... 8.0.0+dfsg-1 (13 versions)
  • every version on: no fix on record
—
python3.133.13.5-2, 3.13.5-2+deb13u1
  • every version up to 3.13.5-2+deb13u2: fixed in 3.13.5-2+deb13u2
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.12.14-r0: fixed in 3.12.14-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.12.14-r0: fixed in 3.12.14-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.12.14-r0: fixed in 3.12.14-r0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 7× in last 7d / 20× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 178 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-27 13:48 UTCEPSS rescore
  11. 2026-09-26 15:59 UTCEPSS rescore
  12. 2026-09-26 00:27 UTCEPSS rescore
  13. 2026-09-23 17:53 UTCEPSS rescore
  14. 2026-09-21 21:01 UTCOSV refresh
  15. 2026-09-20 20:16 UTCEPSS rescore
  16. 2026-09-18 19:28 UTCEPSS rescore
  17. 2026-09-16 14:08 UTCEPSS rescore
  18. 2026-09-16 05:15 UTCEPSS rescore
  19. 2026-09-13 16:47 UTCEPSS rescore
  20. 2026-09-11 14:53 UTCEPSS rescore
  21. 2026-09-10 09:35 UTCEPSS rescore
  22. 2026-09-08 22:01 UTCEPSS rescore
  23. 2026-09-07 16:01 UTCEPSS rescore
  24. 2026-09-06 13:47 UTCEPSS rescore
  25. 2026-09-04 05:06 UTCEPSS rescore
Show 75 more
  1. 2026-09-02 17:08 UTCOSV refresh
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-09-01 04:40 UTCEPSS rescore
  5. 2026-08-30 19:17 UTCEPSS rescore
  6. 2026-08-30 01:22 UTCEPSS rescore
  7. 2026-08-28 21:41 UTCEPSS rescore
  8. 2026-08-27 14:25 UTCEPSS rescore
  9. 2026-08-26 14:46 UTCEPSS rescore
  10. 2026-08-25 13:49 UTCEPSS rescore
  11. 2026-08-23 00:19 UTCEPSS rescore
  12. 2026-08-21 23:49 UTCEPSS rescore
  13. 2026-08-20 22:55 UTCEPSS rescore
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 11:01 UTCEG score recompute
  19. 2026-08-16 11:01 UTCVendor advisory
  20. 2026-08-16 11:01 UTCGHSA enrichment
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-13 01:23 UTCVendor advisory
  25. 2026-08-13 01:23 UTCGHSA enrichment
  26. 2026-08-13 00:41 UTCVendor advisory
  27. 2026-08-13 00:41 UTCGHSA enrichment
  28. 2026-08-12 21:52 UTCEG score recompute
  29. 2026-08-12 21:52 UTCVendor advisory
  30. 2026-08-12 21:52 UTCGHSA enrichment
  31. 2026-08-12 13:51 UTCEPSS rescore
  32. 2026-08-11 00:00 UTCEPSS rescore
  33. 2026-08-09 13:46 UTCEPSS rescore
  34. 2026-08-09 06:45 UTCEG score recompute
  35. 2026-08-09 06:45 UTCVendor advisory
  36. 2026-08-09 06:45 UTCGHSA enrichment
  37. 2026-08-08 16:37 UTCEPSS rescore
  38. 2026-08-06 13:47 UTCEPSS rescore
  39. 2026-08-06 01:27 UTCEG score recompute
  40. 2026-08-06 01:27 UTCVendor advisory
  41. 2026-08-06 01:27 UTCGHSA enrichment
  42. 2026-08-05 19:17 UTCEPSS rescore
  43. 2026-08-04 15:10 UTCEPSS rescore
  44. 2026-08-04 10:39 UTCEPSS rescore
  45. 2026-08-03 10:36 UTCEPSS rescore
  46. 2026-08-02 16:12 UTCEG score recompute
  47. 2026-08-02 16:12 UTCVendor advisory
  48. 2026-08-02 16:12 UTCGHSA enrichment
  49. 2026-08-02 02:27 UTCEPSS rescore
  50. 2026-08-01 04:16 UTCEPSS rescore
  51. 2026-07-30 16:28 UTCEPSS rescore
  52. 2026-07-30 01:30 UTCEPSS rescore
  53. 2026-07-28 15:37 UTCEPSS rescore
  54. 2026-07-26 14:54 UTCEPSS rescore
  55. 2026-07-25 14:18 UTCEPSS rescore
  56. 2026-07-24 14:18 UTCEPSS rescore
  57. 2026-07-23 14:18 UTCEPSS rescore
  58. 2026-07-23 03:16 UTCEG score recompute
  59. 2026-07-22 14:08 UTCEPSS rescore
  60. 2026-07-21 15:25 UTCEPSS rescore
  61. 2026-07-20 17:08 UTCEPSS rescore
  62. 2026-07-19 14:31 UTCEPSS rescore
  63. 2026-07-19 14:31 UTCEPSS rescore
  64. 2026-07-19 02:29 UTCEPSS rescore
  65. 2026-07-18 10:04 UTCEPSS rescore
  66. 2026-07-16 17:03 UTCEPSS rescore
  67. 2026-07-16 07:53 UTCOSV refresh
  68. 2026-07-15 16:57 UTCEPSS rescore
  69. 2026-07-15 16:57 UTCEPSS rescore
  70. 2026-07-15 04:20 UTCNVD updateCVSS v3 → 3.3 · severity → LOW
  71. 2026-07-15 02:00 UTCEPSS rescore
  72. 2026-07-15 02:00 UTCEPSS rescore
  73. 2026-07-15 01:21 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  74. 2026-07-13 22:31 UTCEPSS rescore
  75. 2026-07-13 06:13 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-4519?
CVE-2026-4519 is a low vulnerability published on March 20, 2026. The webbrowser.open() API would accept leading dashes in the URL which could be handled as command line options for certain web browsers. New behavior rejects leading dashes. Users are recommended to sanitize URLs prior to passing to webbrowser.open().
When was CVE-2026-4519 disclosed?
CVE-2026-4519 was first published on March 20, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-4519 actively exploited?
CVE-2026-4519 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-4519?
CVE-2026-4519 has a CVSS v3 base score of 3.3 (NVD).
How do I remediate CVE-2026-4519?
A fix for CVE-2026-4519 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-4519 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-4519

Explore →

Is Your Infrastructure Affected by CVE-2026-4519?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.