CVE-2026-113357
Deferred Deferred - Pending Action

Improper Authorization in GitHub Action Workflow via Comment Manipulation

Publication date: 2026-10-20

Last updated on: 2026-10-20

Assigner: VulnCheck

Description
@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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-20
Last Modified
2026-10-20
Generated
2026-11-09
AI Q&A
2026-10-20
EPSS Evaluated
2026-11-08
NVD
CVE-2026-113357
EUVD
EUVD-2026-104928

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
tester-army @e2e-dev/github 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in @e2e-dev/github before version 0.4.1 allows pull request commenters to hijack CI test reports by exploiting a predictable comment marker. The functions findComment and upsertComment do not verify the comment author, enabling attackers to receive CI results in their own comments and manipulate test outcomes by changing failures to passes or suppressing legitimate reports entirely.

Detection Guidance

Check for unauthorized CI test report modifications in GitHub pull request comments. Look for comments with predictable markers that were not authored by the expected reporter. Review logs for unexpected comment updates or deletions in repositories using @e2e-dev/github before version 0.4.1.

Impact Analysis

If you use @e2e-dev/github before 0.4.1, attackers could alter CI test results in pull requests, leading to false positives or hidden failures. This could mislead teams about code quality, cause incorrect deployments, or hide security issues. The impact depends on whether CI reports are trusted for release decisions.

Compliance Impact

This vulnerability could impact compliance with GDPR and HIPAA by allowing unauthorized users to manipulate CI test reports. Attackers could alter test results to hide failures or falsify compliance evidence, potentially violating integrity requirements in both regulations. GDPR requires data processing integrity while HIPAA mandates accurate audit trails and security of protected health information.

Mitigation Strategies
  • Upgrade @e2e-dev/github to version 0.4.1 or later to apply the authorization fix.
  • Review existing PR comments in affected repositories for unauthorized modifications or hijacked CI reports.
  • Audit GitHub tokens used in CI workflows to ensure they have least-privilege access.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-113357. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...