# CVE-2025-3246: Markdown math block sanitization bypass allows privilege escalation and unauthorized workflow triggers

> Cross-site scripting in Markdown math blocks allows attackers to escalate privileges and trigger unauthorized workflows on GitHub Enterprise Server.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:A/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Apr 2025
- **Updated:** 18 Apr 2025
- **Also known as:** GHSA-m3q4-379j-85vm

## What is CVE-2025-3246?

CVE-2025-3246 is a high-severity cross-site scripting vulnerability in Github Enterprise Server, published on 17 Apr 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

An improper neutralization of input vulnerability was identified in GitHub Enterprise Server that allowed cross-site scripting in GitHub Markdown that used `$$..$$` math blocks.  Exploitation required access to the target GitHub Enterprise Server instance and privileged user interaction with the malicious elements. This vulnerability affected version 3.16.1 of GitHub Enterprise Server and was fixed in version 3.16.2. This vulnerability was reported via the GitHub Bug Bounty program.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-3246?

It affects 1 product.


Products: Github Enterprise Server.

## How do I fix CVE-2025-3246?

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

## Is CVE-2025-3246 being exploited?

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

## Other vulnerabilities in Github Enterprise Server

- [CVE-2024-4985](https://insights.sbomify.com/CVE-2024-4985/): Auth bypass in Enterprise Server (critical 10.0)
- [CVE-2022-23739](https://insights.sbomify.com/CVE-2022-23739/): Missing authorization in GitHub Enterprise Server (critical 9.8)
- [CVE-2022-46255](https://insights.sbomify.com/CVE-2022-46255/): Improper Limitation of a Pathname to a Restricted Directory in GitHub Enterprise Server leading to RCE (critical 9.8)
- [CVE-2021-22869](https://insights.sbomify.com/CVE-2021-22869/): Improper access control in GitHub Enterprise Server allows self-hosted runners to execute outside their control group (critical 9.8)
- [CVE-2024-9487](https://insights.sbomify.com/CVE-2024-9487/): Auth bypass in Enterprise Server (critical 9.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3246 and fix it if it is affected.

What it is: CVE-2025-3246 is a high-severity cross-site scripting vulnerability in Github Enterprise Server, published on 17 Apr 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-3246 in the wild and no public exploit code.

Affected product: Github Enterprise 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-2025-3246/ (Markdown: https://insights.sbomify.com/CVE-2025-3246/index.md)
```

## Sources

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

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