CVE-2026-113357

What it is

@e2e-dev/github before 0.4.1 contains an improper authorization vulnerability that allows pull request commenters to hijack CI test reports by posting comments with the predictable marker. Because findComment and upsertComment in post.ts never check the comment author, attackers can receive results in their own comment and edit failures to passes, or suppress genuine reports entirely.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account, but needs a user to act. Limited direct impact.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-10-20 11:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-20 20:11 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.2% in the next 30 days (EPSS).
• Severity: 5.1 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-10-20 11:17 UTC

Last modified

2026-10-20 20:11 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-863 · Incorrect authorization

Record status

Deferred

Attack profile CVSS 4.0 · 5.1

Attack vector

Network

Complexity

Low

Attack requirements

None

Privileges needed

Low

User interaction

Passive

Confidentiality

None

Integrity

Low

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-113357.md and follow it. Check whether this project is affected by CVE-2026-113357. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge