nday
CVE-2025-3246

Markdown math block sanitization bypass allows privilege escalation and unauthorized workflow triggers

GitHub / GitHub Enterprise Server

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

tags weakness typeXSS accessnetwork productGitHub Enterprise Server product typedeveloper / CI tooling
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

XSS
CWE-79, stated by the CNA GitHub_P and NVD, republishing [email protected]
network
AV:N in 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 (CVSS 4.0) from the CNA GitHub_P
GitHub Enterprise Server
affected products in the CVE record: GitHub · GitHub Enterprise ServerCPE names NVD's analysts give as vulnerable: a:github:enterprise_server
developer / CI tooling
affected products in the CVE record: GitHub · GitHub Enterprise ServerCPE names NVD's analysts give as vulnerable: a:github:enterprise_serverthe product type of GitHub Enterprise Server in nday's product registry
stage
DIS
disclosed
cvss
8.6 HIGH v4.0

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2025-04-17T22:50Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

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.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:H
High: the attacker must evade or get around security measures such as ASLR or DEP, or obtain target-specific secrets
Attack requirements AT:P
Present: success depends on specific deployment or execution conditions, such as a race condition, a non-default setting or a position on the network path
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:A
Active: a user must deliberately do something specific, such as install or run a file or dismiss a warning

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

CVSS 4.0 vector from the CVE record, scored by the CNA GitHub_P.

Event log

+DISdisclosed

CVE record published by GitHub_P. CVSS 8.6, high.

src cvelist · nday , bulk import · raw
{
  "id": 351542,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2025-3246",
  "occurred_at": "2025-04-17T22:50:22.215Z",
  "observed_at": "2026-11-13T05:38:48.939217Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "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",
      "version": "4.0",
      "base_score": 8.6,
      "base_severity": "HIGH"
    },
    "ssvc": {
      "timestamp": "2025-04-18T11:44:25.310657Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "partial"
    },
    "state": "PUBLISHED",
    "date_published": "2025-04-17T22:50:22.215Z",
    "assigner_short_name": "GitHub_P"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.