What is the CVSS score of CVE-2026-27938?

CVE-2026-27938 has a CVSS 3.1 base score of 7.7 (High). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N. EPSS exploitation probability: 0.1%.

Which versions of Github are affected by CVE-2026-27938?

WPGraphQL, a WordPress plugin used to expose site data via GraphQL APIs, contains a critical command injection vulnerability in its CI/CD pipeline that could allow attackers to execute arbitrary code…

How to fix or mitigate CVE-2026-27938?

Within 24 hours: Audit GitHub Actions logs and pull request history for the `develop` to `master` branch to detect any suspicious activity or malicious PR bodies; restrict merge permissions to a minimal set of trusted administrators. Within 7 days: Rotate all GitHub tokens, SSH keys, and secrets that have access to the repository; implement mandatory code review and require pull request approval from security-trained reviewers before any merge. Within 30 days: Update WPGraphQL to version 2.9.1 or later once available; implement branch protection rules requiring signed commits and blocking direct pushes to `master`; establish GitHub Actions hardening practices including use of pinned action versions and least-privilege service account tokens.

Github CVE-2026-27938

HIGH

OS Command Injection (CWE-78)

2026-02-26 security-advisories@github.com

WordPress Command Injection Github

7.7

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

7.7 HIGH

AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

Analysis Generated

Mar 12, 2026 - 21:55 vuln.today

CVE Published

Feb 26, 2026 - 02:16 nvd

HIGH 7.7

DescriptionGitHub Advisory

WPGraphQL provides a GraphQL API for WordPress sites. Prior to version 2.9.1, the wp-graphql/wp-graphql repository contains a GitHub Actions workflow (release.yml) vulnerable to OS command injection through direct use of ${{ github.event.pull_request.body }} inside a run: shell block. When a pull request from develop to master is merged, the PR body is injected verbatim into a shell command, allowing arbitrary command execution on the Actions runner. Version 2.9.1 contains a fix for the vulnerability.

AnalysisAI

Arbitrary command execution in WPGraphQL's GitHub Actions workflow allows attackers with pull request creation privileges to inject shell commands through unvalidated pull request body content, potentially compromising the build environment and repository integrity. The vulnerability affects WPGraphQL versions prior to 2.9.1 and requires low privileges and user interaction to exploit. No patch is currently available for affected deployments.

Technical ContextAI

This vulnerability (CWE-78: OS Command Injection) affects WPGraphQL provides a GraphQL API for WordPress sites.. WPGraphQL provides a GraphQL API for WordPress sites. Prior to version 2.9.1, the wp-graphql/wp-graphql repository contains a GitHub Actions workflow (release.yml) vulnerable to OS command injection through direct use of ${{ github.event.pull_request.body }} inside a run: shell block. When a pull request from develop to master is merged, the PR body is injected verbatim into a shell command, allowing arbitrary command execution on the Actions runner. Version 2.9.1 contains a fix for