CVE-2024-41127Public exploitNetwork attack vector

Pull-request write access via CI artifact injection

Published Aug 2, 2024 · Updated Aug 2, 2024

Code injection in Monkeytype before 24.30.0 allows remote attackers to gain pull-request write access through a crafted CI artifact. The ci-failure-comment.yml workflow reads pr_num.txt from an untrusted workflow artifact without numeric validation and interpolates its contents directly into an actions/github-script JavaScript body. Exploitation requires a malicious pull request whose workflow uploads the artifact and a subsequent workflow_run event, after which injected JavaScript executes with the workflow token's pull-request permissions.

CVSS severity8.4
High
EPSS probability0.88%
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 Monkeytype before 24.30.0 allows remote attackers to gain pull-request write access through a crafted CI artifact. The ci-failure-comment.yml workflow reads pr_num.txt from an untrusted workflow artifact without numeric validation and interpolates its contents directly into an actions/github-script JavaScript body. Exploitation requires a malicious pull request whose workflow uploads the artifact and a subsequent workflow_run event, after which injected JavaScript executes with the workflow token's pull-request permissions.

The record

CVE
CVE-2024-41127
Published
Aug 2, 2024
Updated
Aug 2, 2024
Vendor
Monkeytype
Product
Monkeytype
Classifications
CWE-94, CWE-74, T1059.007
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 2, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 2, 2024Record 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=0 <24.30.0
  2. Affected versionversion=< 24.30.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Monkeytype · Monkeytypeversion=0 <24.30.0; version=< 24.30.0

Published CVSS scores

8.4GitHub, Inc.CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

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')
CWE-74Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
T1059.007Command and Scripting Interpreter: JavaScript

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