Pull-request build triggering via unrestricted HTTP method
Published May 27, 2026 · Updated May 27, 2026
CSRF in Jenkins GitHub Integration Plugin 0.7.3 and earlier allows remote attackers to trigger pull-request builds. The affected HTTP endpoint processes a state-changing build request without requiring POST, allowing a cross-origin request to invoke it. Exploitation requires a victim to load an attacker-controlled request; the documented consequence is an unintended build trigger.
Summary
What happened
CSRF in Jenkins GitHub Integration Plugin 0.7.3 and earlier allows remote attackers to trigger pull-request builds. The affected HTTP endpoint processes a state-changing build request without requiring POST, allowing a cross-origin request to invoke it. Exploitation requires a victim to load an attacker-controlled request; the documented consequence is an unintended build trigger.
The record
- CVE
- CVE-2026-48925
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Vendor
- Jenkins Project
- Product
- GitHub Integration Plugin
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 27, 2026CVE publishedPublication date reported by the CVE source.
- May 27, 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=0 <=0.7.3
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.
Public exploit references
No public exploit references are available in this record.
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