CVE-2026-115975
HighCVSS 7.1Summary
A broken access control vulnerability in the JiraController component of Cervantes version v1.3-beta could allow an attacker to create, edit, or delete Jira tickets for vulnerabilities in other projects. The flaw stems from insufficient permission checks.
Risk Assessment
An attacker could manipulate Jira tickets in projects they should not have access to, potentially leading to data corruption or sabotage of the vulnerability management process. This could disrupt security and development teams.
Recommendation
Update Cervantes to a version newer than v1.3-beta that fixes the access control issue. If no update is available, restrict access to the JiraController and implement additional permission checks.
Other vulnerabilities in Cervantes
See all- CVE-2026-115998Medium
IDOR in Cervantes version v1.3-beta could allow an authenticated attacker to access sensitive findings, proof-of-concept details, credentials, and client information from projects they do not belong to. Additionally, they can modify finding statuses and transfer findings to their own projects, compromising data confidentiality and integrity.
- CVE-2026-115994Medium
BOLA in Cervantes version v1.3-beta could allow an attacker to modify or delete targets belonging to other projects without authorization, compromising the integrity of penetration testing scopes, results, and associated security reports.
- CVE-2026-115993Medium
A stored XSS vulnerability exists in the “Notes” field of the Checklists in Cervantes version v1.3-beta. An attacker can store malicious code that is later executed in another user's browser with elevated privileges.
Original NVD description (English source)
Broken access control in JiraController in Cervantes version v1.3-beta could allow an attacker to create, edit, or delete Jira tickets for vulnerabilities in other projects
Vulnerability data from NVD (NIST) · CISA KEV · EPSS