Remote code execution via privileged fork checkout
Published May 11, 2026 · Updated May 11, 2026
Code injection in OWASP Bug Logging Tool before 2.1.2 allows remote attackers to execute code through a crafted pull request. The pre-commit-fix.yaml workflow uses pull_request_target, checks out an attacker's fork, and executes its code with a write-enabled token. Exploitation requires the privileged workflow to process the pull request, after which the injected code can modify repository content.
Summary
What happened
Code injection in OWASP Bug Logging Tool before 2.1.2 allows remote attackers to execute code through a crafted pull request. The pre-commit-fix.yaml workflow uses pull_request_target, checks out an attacker's fork, and executes its code with a write-enabled token. Exploitation requires the privileged workflow to process the pull request, after which the injected code can modify repository content.
The record
- CVE
- CVE-2026-42603
- Published
- May 11, 2026
- Updated
- May 11, 2026
- Vendor
- OWASP ModSecurity
- Product
- OWASP Bug Logging Tool
- Classifications
- CWE-95, CWE-94, T1195.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 11, 2026CVE publishedPublication date reported by the CVE source.
- May 11, 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.
- Affected versionversion=< 2.1.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
Public exploit references
- GHSA-cgvj-qg2h-cqfh proof of conceptproof of concept · demonstrated
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