Skip to content
major vulnerability· requires attention

Affects widely-used GitHub Enterprise Server; XSS could exfiltrate data via search UI, impacting many organizations.

Web

CVE-2025-13744

8.4
High
EPSS 0.21%Patch availableJan 7, 2026

XSS in GitHub Enterprise Server filter renders attacker-controlled HTML.

common questions

Is CVE-2025-13744 being exploited?

Not confirmed. CVE-2025-13744 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.21% probability of exploitation in the next 30 days.

How severe is CVE-2025-13744?

CVE-2025-13744 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-13744?

Yes. A fix has been recorded for CVE-2025-13744. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-13744 affect?

CVE-2025-13744 affects GitHub Enterprise Server < 3.20. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-13744?

Upgrade to fixed version 3.19.1 or newer ASAP

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
GitHub Enterprise Server < 3.20
impact

Exfiltration of sensitive data via stored XSS in the search/filter UI; requires edit-permissions on milestones/issues/PRs.

action required

Immediate action required

affected versions
GitHub Enterprise Server
  • affected>= 3.14.0 and <= 3.14.19
  • affected>= 3.15.0 and <= 3.15.14
  • affected>= 3.16.0 and <= 3.16.10
  • affected>= 3.17.0 and <= 3.17.7
  • affected>= 3.18.0 and <= 3.18.1
  • affected>= 3.19 and <= 3.19.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free