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 45% 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
56%
KEV
Not listed

Published

May 22, 2026

Last Modified

August 27, 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

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntunode-shell-quote (1.8.3+~1.7.5-1ubuntu0.1~esm1) @ resolute2026-08-27ubuntu
redhatopenshift4/ose-console:17870285592026-08-26redhat
redhatopenshift4/ose-console-rhel9:17870541592026-08-26redhat
redhatansible-automation-platform/automation-portal:17858542262026-08-05redhat
redhatopenshift4/ose-console-rhel9:17852785692026-08-05redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17847137412026-07-28redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17847215812026-07-28redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17847246992026-07-28redhat
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
redhatquay/quay-rhel8:17824877172026-06-30redhat
redhatopenshift4/ose-console-rhel9:17822243902026-06-30redhat
redhatopenshift4/ose-console-rhel9:17823086752026-06-30redhat
redhatrhdh/rhdh-hub-rhel9:17827612442026-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:17809163452026-06-15redhat
redhatopenshift-service-mesh/kiali-rhel8:17809165362026-06-15redhat
redhatopenshift-service-mesh/kiali-rhel9:17809164782026-06-15redhat
redhatopenshift-service-mesh/kiali-rhel9:17809163922026-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

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-shell-quote1.7.4+~1.7.1-11.7.4+~1.7.1-1+deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-shell-quote1.7.4+~1.7.1-11.7.4+~1.7.1-1+deb13u1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-shell-quote1.7.4+~1.7.1-1, 1.7.4+~1.7.1-2, 1.8.3+~1.7.5-11.8.4+~1.7.5-1
npm(1)
PackageVulnerable rangeFixed inDependents
shell-quote1.8.4

Weakness Classification(2)

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

Additional Vendor Advisories

(9)

Data Freshness Timeline

(refreshed 23× in last 7d / 123× 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 233 total refreshes for this CVE.

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

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 August 27, 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 44.5% 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.