CVE-2025-50738

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 2.4% (84th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2025-23004 (ENISA EUVD) · GHSA-hfcf-79gh-f3jc (GitHub Security Advisories) · GO-2025-3831 (OSV.dev)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 2.4%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

The Memos application, up to version v0.24.3, allows for the embedding of markdown images with arbitrary URLs. When a user views a memo containing such an image, their browser automatically fetches the image URL without explicit user consent or interaction beyond viewing the memo. This can be exploited by an attacker to disclose the viewing user's IP address, browser User-Agent string, and potentially other request-specific information to the attacker-controlled server, leading to information disclosure and user tracking.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
2.4%
EPSS %ILE
84th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
2.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 29, 2025

Last Modified

August 22, 2025

Advisory Details (3)

Auto-updated Oct 9, 2026
Patch available.
Web page

Stored XSS via SVG file upload · Issue #4707 · usememos/memos · GitHub

https://github.com/usememos/memos/issues/4707#issuecomment-2898504237
Web page

GitHub - usememos/memos: A personal timeline for quick notes. Write short memos, find them later by search, tag, or date. Open source and self-hosted. · GitHub

https://github.com/usememos/memos
Web page

Vulnerability-Research/CVE-2025-50738 at main · fai1424/Vulnerability-Research · GitHub

https://github.com/fai1424/Vulnerability-Research/tree/main/CVE-2025-50738

Vendor Advisories for CVE-2025-50738(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/usememos/memos @ 0.24.4 (fixes < 0.24.4)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/usememos/memos—
  • every version up to 0.24.4: fixed in 0.24.4
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 45× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 258 rows on record for this CVE, as 98 entries (2 repeats merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 158 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  2. 2026-11-13 09:59 UTCEchelonGraph re-scored
  3. 2026-11-13 09:59 UTCGHSA enrichmentGHSA-hfcf-79gh-f3jc · GitHub severity MODERATE
  4. 2026-11-12 16:32 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  5. 2026-11-12 11:16 UTCEchelonGraph re-scored
  6. 2026-11-12 11:16 UTCGHSA enrichmentGHSA-hfcf-79gh-f3jc · GitHub severity MODERATE
  7. 2026-11-11 16:36 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  8. 2026-11-11 12:33 UTCEchelonGraph re-scored
  9. 2026-11-11 12:33 UTCGHSA enrichmentGHSA-hfcf-79gh-f3jc · GitHub severity MODERATE
  10. 2026-11-10 16:40 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  11. 2026-11-10 13:49 UTCEchelonGraph re-scored
  12. 2026-11-10 13:49 UTCGHSA enrichmentGHSA-hfcf-79gh-f3jc · GitHub severity MODERATE
  13. 2026-11-09 16:33 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  14. 2026-11-09 15:06 UTCEchelonGraph re-scored
  15. 2026-11-09 15:06 UTCGHSA enrichmentGHSA-hfcf-79gh-f3jc · GitHub severity MODERATE
  16. 2026-11-08 16:37 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  17. 2026-11-08 16:23 UTCGHSA enrichmentGHSA-hfcf-79gh-f3jc · GitHub severity MODERATE
  18. 2026-11-07 17:35 UTCEchelonGraph re-scored
  19. 2026-11-07 17:35 UTCGHSA enrichmentGHSA-hfcf-79gh-f3jc · GitHub severity MODERATE
  20. 2026-11-07 16:37 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  21. 2026-11-06 18:51 UTCEchelonGraph re-scored
  22. 2026-11-06 18:51 UTCGHSA enrichmentGHSA-hfcf-79gh-f3jc · GitHub severity MODERATE
  23. 2026-11-06 16:34 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  24. 2026-11-05 20:08 UTCEchelonGraph re-scored
  25. 2026-11-05 20:08 UTCGHSA enrichmentGHSA-hfcf-79gh-f3jc · GitHub severity MODERATE
Show 73 more
  1. 2026-11-05 16:35 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  2. 2026-11-05 14:25 UTCOSV refresh
  3. 2026-11-04 21:24 UTCEchelonGraph re-scored
  4. 2026-11-04 21:24 UTCGHSA enrichmentGHSA-hfcf-79gh-f3jc · GitHub severity MODERATE
  5. 2026-11-04 16:33 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  6. 2026-11-03 22:40 UTCEchelonGraph re-scored
  7. 2026-11-03 22:40 UTCGHSA enrichmentGHSA-hfcf-79gh-f3jc · GitHub severity MODERATE
  8. 2026-11-03 16:45 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  9. 2026-11-02 23:57 UTCEchelonGraph re-scored
  10. 2026-11-02 23:56 UTCGHSA enrichmentGHSA-hfcf-79gh-f3jc · GitHub severity MODERATE
  11. 2026-11-02 16:43 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  12. 2026-11-02 01:12 UTCEchelonGraph re-scored
  13. 2026-11-02 01:12 UTCGHSA enrichmentGHSA-hfcf-79gh-f3jc · GitHub severity MODERATE
  14. 2026-11-01 16:33 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  15. 2026-11-01 08:05 UTCGHSA enrichmentGHSA-hfcf-79gh-f3jc · GitHub severity MODERATE
  16. 2026-11-01 02:27 UTCEchelonGraph re-scored
  17. 2026-10-31 16:31 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  18. 2026-10-31 03:43 UTCEchelonGraph re-scored
  19. 2026-10-30 16:33 UTCEPSS rescoreEPSS 2.4% · 84th percentile
  20. 2026-10-30 05:00 UTCEchelonGraph re-scored
  21. 2026-10-29 16:31 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  22. 2026-10-29 06:16 UTCEchelonGraph re-scored
  23. 2026-10-28 16:30 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  24. 2026-10-28 07:33 UTCEchelonGraph re-scored
  25. 2026-10-27 16:30 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  26. 2026-10-27 08:49 UTCEchelonGraph re-scored
  27. 2026-10-26 16:30 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  28. 2026-10-26 08:27 UTCEchelonGraph re-scored
  29. 2026-10-25 16:31 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  30. 2026-10-25 16:20 UTCEchelonGraph re-scored
  31. 2026-10-25 09:43 UTCEchelonGraph re-scored
  32. 2026-10-24 16:31 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  33. 2026-10-24 10:59 UTCEchelonGraph re-scored
  34. 2026-10-23 16:30 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  35. 2026-10-23 12:11 UTCEchelonGraph re-scored
  36. 2026-10-22 16:33 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  37. 2026-10-22 13:27 UTCEchelonGraph re-scored
  38. 2026-10-21 16:31 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  39. 2026-10-21 14:42 UTCEchelonGraph re-scored
  40. 2026-10-20 16:31 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  41. 2026-10-20 15:28 UTCEchelonGraph re-scored
  42. 2026-10-19 16:31 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  43. 2026-10-18 17:22 UTCEchelonGraph re-scored
  44. 2026-10-18 16:31 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
  45. 2026-10-18 05:28 UTCEchelonGraph re-scored
  46. 2026-10-17 18:38 UTCEchelonGraph re-scored
  47. 2026-10-17 16:33 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
  48. 2026-10-16 19:49 UTCEchelonGraph re-scored
  49. 2026-10-16 16:39 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
  50. 2026-10-15 17:06 UTCEchelonGraph re-scored
  51. 2026-10-15 16:31 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
  52. 2026-10-14 16:31 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  53. 2026-10-14 11:06 UTCEchelonGraph re-scored
  54. 2026-10-13 16:33 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  55. 2026-10-12 16:59 UTCEchelonGraph re-scored
  56. 2026-10-12 16:33 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  57. 2026-10-11 20:33 UTCEchelonGraph re-scored
  58. 2026-10-11 18:44 UTCEchelonGraph re-scored
  59. 2026-10-11 15:20 UTCEchelonGraph re-scored
  60. 2026-10-11 13:47 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  61. 2026-10-10 19:59 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  62. 2026-10-09 20:06 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  63. 2026-10-08 17:10 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  64. 2026-10-07 23:47 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  65. 2026-10-06 15:17 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  66. 2026-10-05 17:42 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  67. 2026-10-04 23:21 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  68. 2026-10-03 14:24 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  69. 2026-10-02 08:11 UTCOSV refresh
  70. 2026-10-01 19:49 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  71. 2026-09-30 15:02 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  72. 2026-09-28 13:50 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  73. 2026-09-26 15:58 UTCEPSS rescoreEPSS 2.1% · 80th percentile

Frequently asked(5)

What is CVE-2025-50738?
CVE-2025-50738 is a critical-severity vulnerability; its CVE record was published on July 29, 2025. The Memos application, up to version v0.24.3, allows for the embedding of markdown images with arbitrary URLs. When a user views a memo containing such an image, their browser automatically fetches the image URL without explicit user consent or interaction beyond viewing the memo. This can be…
When was the CVE record for CVE-2025-50738 published?
The CVE record for CVE-2025-50738 was published on July 29, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 22, 2025; the record at its source may have been updated since.
Is CVE-2025-50738 actively exploited?
CVE-2025-50738 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.4% probability of exploitation in the next 30 days (84th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-50738?
CVE-2025-50738 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-50738?
A fix for CVE-2025-50738 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-50738 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-50738

Explore →

Is Your Infrastructure Affected by CVE-2025-50738?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.