# CVE-2026-19369: KS-GEN-AI jira-mcp-server add_attachment_from_public_url index.ts axios.get server-side request forgery

> An attacker can exploit a server-side request forgery vulnerability in the jira-mcp-server library to access internal resources via the add_attachment_from_public_url function.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-rmrp-j9qh-xwh9

## What is CVE-2026-19369?

CVE-2026-19369 is a medium-severity server-side request forgery vulnerability in KS-GEN-AI jira-mcp-server, published on 9 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in KS-GEN-AI jira-mcp-server 0.2.0. This affects the function axios.get of the file src/index.ts of the component add_attachment_from_public_url. The manipulation of the argument imageUrl results in server-side request forgery. The attack requires a local approach. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-19369?


## How do I fix CVE-2026-19369?

No fix has been published for CVE-2026-19369 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19369 being exploited?

There is no known exploitation of CVE-2026-19369 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19369 and fix it if it is affected.

What it is: CVE-2026-19369 is a medium-severity server-side request forgery vulnerability in KS-GEN-AI jira-mcp-server, published on 9 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19369 in the wild and no public exploit code.

Affected product: KS-GEN-AI jira-mcp-server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19369/ (Markdown: https://insights.sbomify.com/CVE-2026-19369/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19369
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19369
- OSV: https://osv.dev/vulnerability/CVE-2026-19369

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19369/
Summaries are generated and may contain mistakes; the official description above is the record.