Case · DiggingBeagle record

MCP Atlassian issue-link removal could turn into issue deletion

Path traversal in link_id changed the effective DELETE REST endpoint.

Public disclosure: Nov 8, 2026

Scope

The underlying Jira credential may delete issues, while the MCP client may call link removal but not the dedicated issue-deletion tool. An unvalidated link identifier was normalized from issueLink to the issue resource; 0.24.1 restricts the identifier to digits.

Assessment profile

Assessment method
Setting
research demonstration
Exploitation
demonstrated
Evidence
Grade B
Remediation
patch available
AI role
AGAINST AI
Basis and provenance

Scoped Claim(s) link to SRC-2026-DB233-GHSA-8FFX-6C2G-75CC; reviewed as vulnerability in research_demonstration. Only reported controlled behavior or proof-of-concept is established; no production victim or impact magnitude is measured.

Assessed Nov 10, 2026 using diggingbeagle.assessment/1.

At a glance

Mechanism and trust boundary

  1. 01

    Precondition and trust context

    The underlying Jira credential may delete issues, while the MCP client may call link removal but not the dedicated issue-deletion tool.

  2. 02

    Crossed boundary

    An unvalidated link identifier was normalized from issueLink to the issue resource; 0.24.1 restricts the identifier to digits.

  3. 03

    Observed limit

    Requires Jira delete permissions; no confirmed accidental production issue deletion.

Timeline

  1. Nov 8, 2026
    Event type unspecified

    Initial documented finding

    MCP Atlassian issue-link removal could turn into issue deletion

  2. Nov 8, 2026
    disclosure

    Public disclosure

Claims & evidence

CLM-DB233-ATL-GHSA-8FFX-6C2G-75CC-01The GHSA-8ffx-6c2g-75cc advisory documents that an unvalidated link identifier was normalized from issueLink to the issue resource; 0.24.1 restricts the identifier to digits.supported

Basis: reported finding

Link to claim
CLM-DB233-ATL-GHSA-8FFX-6C2G-75CC-02The disclosed precondition is: The underlying Jira credential may delete issues, while the MCP client may call link removal but not the dedicated issue-deletion tool.supported

Basis: reported finding

Link to claim

Controls and mitigations

  • Require numeric issue-link identifiers and construct REST paths without concatenating untrusted segments; the fix is reported in 0.24.1.
  • Give the MCP service credential only those Jira permissions necessary for the intended link operation.

Unknowns and contradictions

  • Requires Jira delete permissions; no confirmed accidental production issue deletion.

Sources and citation

Material revision history

  1. Nov 10, 2026 · Published version · first publication · revision 235