CVE Intelligence
High Access control

CVE-2026-115975 — Broken access control in JiraController

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

Published Oct 24, 2026 · Updated Oct 26, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Grayback

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+2
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.22%
ahead of 12% of scored CVEs · Oct 29, 2026
Affects
CervantesSec
Cervantes
CVSS base
7.1
High · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (CervantesSec Cervantes).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
CervantesSec Cervantes ≥ alpha 0.3 and ≤ 1.3-beta Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.1 CVSS 3.1 High 2.8 4.2 772f0079-75c2-41ca-913e-d9072716578b via NIST National Vulnerability Database
7.1 CVSS 3.1 High — — Grayback via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N (score shown at the top: 772f0079-75c2-41ca-913e-d9072716578b)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-862 · Missing Authorization

Other CVEs with this weakness →

EPSS over time FIRST

Oct 24, 2026 → Oct 29, 2026 · 6 reading(s) · max 0.29%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Audit administrative actions and access to resources outside each user’s normal pattern.
web/proxy/WAF logsnetwork IDS/IPSauthentication logsapplication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Received → Deferred
    Oct 26, 2026 · NIST National Vulnerability Database
  • Affected products added · cervantessec/cervantes
    Oct 24, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 24, 2026
  • CVSS changed · 7.1
    Oct 24, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 24, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 24, 2026 · Alertas do Telegram
  • CVE published
    Oct 24, 2026 · Grayback

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 24, 2026 – Oct 24, 2026
  • 1× Official description updated · Oct 24, 2026 – Oct 24, 2026

References

2 on the record

Elsewhere on this site

CervantesSec
every CVE for this vendor
Access control
same class
CWE-862
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-115998 IDOR: User reads and modifies findings from other people's projects 6d
  • CVE-2026-115994 BOLA Allows Cross-Project Target Tampering 6d
  • CVE-2026-115993 Stored XSS in the “Notes” field of project checklists 6d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-115975 is "Broken access control in JiraController", rated High. It affects Cervantes (CervantesSec); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.1 describes technical severity. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.