@e2e-dev/github before 0.4.1 CI Report Hijacking via Predictable Comment Marker
Published Oct 20, 2026 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
@e2e-dev/github before 0.4.1 CI Report Hijacking via Predictable Comment Marker
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
@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.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- GitHub advisory ↗
- Patch commit ↗
- Source repository ↗
- Source repository ↗
- VulnCheck Advisory: @e2e-dev/github before 0.4.1 CI Report Hijacking via Predictable Comment Marker ↗
Record history
Published Oct 20, 2026 · Last refreshed Nov 3, 2026