CVE-2026-9277

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8%, top 46% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — Patch released this weekElevated
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.1Exploit: Elevated riskExposed: 0

A fix is available — apply it.

shell-quote's quote() function did not validate object-token inputs against the operator model used by parse(). The .op field was backslash-escaped character by character using /(.)/g, which in JavaScript does not match line terminators (\n, \r, U+2028, U+2029). A line terminator in .op therefore passed through unescaped into the output; POSIX shells treat a literal newline as a command separator, so any content after it would execute as a second command. The vulnerable code path is reachable in two ways: (1) direct construction of { op: '...\n...' } from external input, and (2) via parse(cmd, envFn) when envFn returns object tokens whose .op is attacker-influenced. Both are documented API surface. Fixed by replacing the per-character escape with strict shape validation: .op must match the parser's control-operator allowlist; { op: 'glob', pattern } validates pattern and forbids line terminators; { comment } validates comment and forbids line terminators; any other object shape throws TypeError.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
52(Track)
EG Risk 52/100SSVC: Track

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
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
54%
KEV
Not listed

Published

May 22, 2026

Last Modified

July 23, 2026

Advisory Details (3)

Auto-updated Jun 3, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

shell-quote quote() does not escape newlines in object .op values · Advisory · ljharb/shell-quote · GitHub

https://github.com/ljharb/shell-quote/security/advisories/GHSA-w7jw-789q-3m8p
generic🟡 PoC Available

oss-security - CVE-2026-9277: shell-quote before 1.8.4 command injection in quote()

http://www.openwall.com/lists/oss-security/2026/05/23/2
generic

GitHub - ljharb/shell-quote · GitHub

https://github.com/ljharb/shell-quote

Vendor Advisories for CVE-2026-9277(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(23)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntunode-shell-quote (1.8.3+~1.7.5-1ubuntu0.1~esm1) @ resolute2026-07-26ubuntu
redhatopenshift4/ose-console-rhel9:17837181572026-07-22redhat
redhatquay/quay-rhel8:17843519662026-07-21redhat
redhatrhmtc/openshift-migration-ui-rhel8:17836905322026-07-20redhat
redhatquay/quay-rhel9:17839558462026-07-16redhat
redhatrhdh/rhdh-hub-rhel9:17834481842026-07-08redhat
redhatopenshift4/ose-console-rhel9:17829117112026-07-07redhat
redhatcluster-observability-operator/troubleshooting-panel-console-plugin-rhel9:17828394942026-07-01redhat
redhatopenshift4/ose-console-rhel9:17822243902026-06-30redhat
redhatquay/quay-rhel8:17824877172026-06-30redhat
redhatrhdh/rhdh-hub-rhel9:17827612442026-06-30redhat
redhatopenshift4/ose-console-rhel9:17823086752026-06-30redhat
redhatquay/quay-rhel8:17819373572026-06-25redhat
redhatdiscovery/discovery-ui-rhel9:17821669522026-06-24redhat
redhatquay/quay-rhel8:17818780702026-06-23redhat
redhatcryostat/cryostat-openshift-console-plugin-rhel9:4.2.0-102026-06-22redhat
redhatsatellite/iop-vulnerability-frontend-rhel9:17810324952026-06-16redhat
redhatrhdh/rhdh-hub-rhel9:17811873422026-06-16redhat
redhatopenshift-service-mesh/kiali-rhel9:17809164782026-06-15redhat
redhatopenshift-service-mesh/kiali-rhel9:17809163922026-06-15redhat
redhatopenshift-service-mesh/kiali-rhel8:17809165362026-06-15redhat
redhatopenshift-service-mesh/kiali-rhel9:17809163452026-06-15redhat
redhatopenshift-service-mesh/kiali-rhel9:17809974382026-06-15redhat

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

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
shell-quote—1.8.4—

Weakness Classification(2)

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

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 11× in last 7d / 38× 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.

  1. 2026-07-26 14:54 UTCEPSS rescore
  2. 2026-07-26 08:07 UTCEG score recompute
  3. 2026-07-26 08:07 UTCVendor advisory
  4. 2026-07-25 14:18 UTCEPSS rescore
  5. 2026-07-24 14:18 UTCEPSS rescore
  6. 2026-07-23 14:18 UTCEPSS rescore
  7. 2026-07-23 03:23 UTCEG score recompute
  8. 2026-07-22 14:08 UTCEPSS rescore
  9. 2026-07-21 15:25 UTCEPSS rescore
  10. 2026-07-21 15:25 UTCEPSS rescore
  11. 2026-07-20 17:08 UTCEPSS rescore
  12. 2026-07-19 14:31 UTCEPSS rescore
  13. 2026-07-19 02:29 UTCEPSS rescore
  14. 2026-07-18 10:04 UTCEPSS rescore
  15. 2026-07-17 18:59 UTCOSV refresh
  16. 2026-07-16 17:03 UTCEPSS rescore
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 02:00 UTCEPSS rescore
  19. 2026-07-13 22:31 UTCEPSS rescore
  20. 2026-07-13 06:13 UTCEPSS rescore
  21. 2026-07-12 05:46 UTCEPSS rescore
  22. 2026-07-11 08:27 UTCEPSS rescore
  23. 2026-07-09 19:10 UTCEPSS rescore
  24. 2026-07-08 15:16 UTCEPSS rescore
  25. 2026-07-07 13:46 UTCEPSS rescore
Show 65 more
  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-05 02:31 UTCEPSS rescore
  4. 2026-07-04 06:31 UTCEPSS rescore
  5. 2026-07-04 06:31 UTCEPSS rescore
  6. 2026-07-01 15:07 UTCEPSS rescore
  7. 2026-06-30 23:22 UTCEPSS rescore
  8. 2026-06-29 16:38 UTCVendor advisory
  9. 2026-06-29 14:06 UTCEPSS rescore
  10. 2026-06-28 14:07 UTCEPSS rescore
  11. 2026-06-28 07:49 UTCVendor advisory
  12. 2026-06-28 04:56 UTCEPSS rescore
  13. 2026-06-27 19:32 UTCVendor advisory
  14. 2026-06-27 07:22 UTCVendor advisory
  15. 2026-06-27 03:08 UTCEPSS rescore
  16. 2026-06-26 19:13 UTCVendor advisory
  17. 2026-06-26 03:18 UTCVendor advisory
  18. 2026-06-25 13:57 UTCVendor advisory
  19. 2026-06-25 13:50 UTCEPSS rescore
  20. 2026-06-24 14:05 UTCEPSS rescore
  21. 2026-06-23 21:33 UTCEPSS rescore
  22. 2026-06-22 14:25 UTCEPSS rescore
  23. 2026-06-21 14:56 UTCEPSS rescore
  24. 2026-06-21 01:59 UTCEPSS rescore
  25. 2026-06-19 19:26 UTCEPSS rescore
  26. 2026-06-18 17:52 UTCEPSS rescore
  27. 2026-06-17 23:10 UTCVendor advisory
  28. 2026-06-17 17:53 UTCEPSS rescore
  29. 2026-06-17 10:57 UTCVendor advisory
  30. 2026-06-16 19:24 UTCVendor advisory
  31. 2026-06-16 17:53 UTCEPSS rescore
  32. 2026-06-16 03:04 UTCVendor advisory
  33. 2026-06-15 17:49 UTCEPSS rescore
  34. 2026-06-15 17:49 UTCEPSS rescore
  35. 2026-06-15 14:54 UTCVendor advisory
  36. 2026-06-14 23:18 UTCEPSS rescore
  37. 2026-06-14 22:15 UTCVendor advisory
  38. 2026-06-14 10:05 UTCVendor advisory
  39. 2026-06-13 23:00 UTCEPSS rescore
  40. 2026-06-13 21:53 UTCVendor advisory
  41. 2026-06-13 08:49 UTCVendor advisory
  42. 2026-06-12 23:12 UTCEPSS rescore
  43. 2026-06-12 23:12 UTCEPSS rescore
  44. 2026-06-12 20:38 UTCVendor advisory
  45. 2026-06-12 08:26 UTCVendor advisory
  46. 2026-06-11 20:17 UTCVendor advisory
  47. 2026-06-11 14:00 UTCEPSS rescore
  48. 2026-06-10 22:19 UTCEPSS rescore
  49. 2026-06-10 13:22 UTCEPSS rescore
  50. 2026-06-08 14:17 UTCEPSS rescore
  51. 2026-06-07 15:25 UTCEPSS rescore
  52. 2026-06-06 13:47 UTCEPSS rescore
  53. 2026-06-05 22:47 UTCEPSS rescore
  54. 2026-06-05 06:10 UTCEPSS rescore
  55. 2026-06-04 13:12 UTCEPSS rescore
  56. 2026-06-02 20:13 UTCEPSS rescore
  57. 2026-06-01 13:52 UTCEPSS rescore
  58. 2026-05-31 22:30 UTCEPSS rescore
  59. 2026-05-31 00:16 UTCEPSS rescore
  60. 2026-05-29 13:44 UTCEPSS rescore
  61. 2026-05-28 13:44 UTCEPSS rescore
  62. 2026-05-27 13:40 UTCEPSS rescore
  63. 2026-05-26 13:44 UTCEPSS rescore
  64. 2026-05-26 07:18 UTCEPSS rescore
  65. 2026-05-23 03:58 UTCEG score recompute

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

Frequently asked(5)

What is CVE-2026-9277?
CVE-2026-9277 is a high vulnerability published on May 22, 2026. shell-quote's quote() function did not validate object-token inputs against the operator model used by parse(). The .op field was backslash-escaped character by character using /(.)/g, which in JavaScript does not match line terminators (\n, \r, U+2028, U+2029). A line terminator in .op therefore…
When was CVE-2026-9277 disclosed?
CVE-2026-9277 was first published in the National Vulnerability Database on May 22, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9277 actively exploited?
CVE-2026-9277 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 45.7% of all scored CVEs.
What is the CVSS score of CVE-2026-9277?
CVE-2026-9277 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-9277?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9277, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-9277?

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

Start Free Scan →Browse All CVEs