CVE-2026-27701Public exploitNetwork attack vector

CI token compromise via pull-request title injection

Published Feb 25, 2026 · Updated Feb 25, 2026

Code injection in the LiveCodes i18n-update-pull workflow allows attackers to execute JavaScript through a crafted pull-request title. An actions/github-script step embeds github.event.issue.title directly into a JavaScript template literal, so a backtick closes the string and injects statements. Exploitation requires a malicious pull request to be merged and a trusted collaborator to post the workflow command; injected code can read runner secrets and issue unauthorized GitHub API requests as the CI bot.

CVSS severity8.8
High
EPSS probability0.25%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Code injection in the LiveCodes i18n-update-pull workflow allows attackers to execute JavaScript through a crafted pull-request title. An actions/github-script step embeds github.event.issue.title directly into a JavaScript template literal, so a backtick closes the string and injects statements. Exploitation requires a malicious pull request to be merged and a trusted collaborator to post the workflow command; injected code can read runner secrets and issue unauthorized GitHub API requests as the CI bot.

The record

CVE
CVE-2026-27701
Published
Feb 25, 2026
Updated
Feb 25, 2026
Vendor
LiveCodes
Product
LiveCodes
Classifications
CWE-94, T1059.007
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Feb 25, 2026CVE publishedPublication date reported by the CVE source.
  2. Feb 25, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< e151c64c2bd80d2d53ac1333f1df9429fe6a1a11

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

LiveCodes · LiveCodesversion=< e151c64c2bd80d2d53ac1333f1df9429fe6a1a11

Published CVSS scores

8.8GitHub, Inc.CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-94Improper Control of Generation of Code ('Code Injection')
T1059.007JavaScript/JScript

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo