Disclosed weakness · no CVE recorded

Web content could use the Atlassian MCP operator’s credentials

mcp-atlassian maintainers · mcp-atlassian · Jira and Confluence MCP server

First documented disclosure · Review checkpoint

Summary

On qualifying HTTP deployments, a browser could cause tool requests to run under the operator’s Atlassian identity.

Severity and exploitation evidence

Medium · numeric CVSS score not recorded. Severity source.

Exploitation not established: The maintainer reports an internal audit finding. The advisory identifies no malicious use.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The server used fallback credentials without checking the requesting origin and host.

Conditions required

A browser can reach the HTTP listener and the server permits global credential fallback or ignores header authentication.

Potential impact

A web page could read or change Atlassian resources within the operator’s permissions and the enabled tools.

Affected versions and configurations

Before 0.24.5.

Fix and mitigation status

0.24.5.

Practical next steps

Upgrade to 0.24.6 or later. Disable both credential-fallback options or enable HTTP host and origin protection.

Operating lesson

Check the browser origin when a server supplies credentials on behalf of a caller.

Evidence and limits

The maintainer traced this issue to an internal audit and published the patch and advisory November 16. The advisory provides a severity label without a numeric score.

Sources