CVE-2025-50738: memos · n/a
Affects memosSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 2.3% chance of exploitation in 30 days – higher than 83% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 29 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubusememos/memospkg:github/usememos/memosOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate this vulnerability, European organizations should take immediate and specific actions beyond generic advice: 1) Disable or restrict the rendering of markdown images with external URLs within the Memos application until a patch is available. This can be done by configuring the application to sanitize or block image URLs that point to external domains or by disabling image embedding features entirely. 2) Implement network-level controls such as web proxy filtering or firewall rules to monitor and restrict outbound HTTP(S) requests originating from the Memos application, especially those targeting unknown or suspicious external domains. 3) Educate users about the risks of viewing untrusted memos or content containing external images, emphasizing caution with unknown senders or sources. 4) Monitor network traffic for unusual or unexpected requests to external servers that could indicate exploitation attempts. 5) Engage with the Memos application vendor or community to obtain patches or updates addressing this vulnerability and prioritize their deployment once available. 6) Consider deploying Content Security Policy (CSP) headers or similar browser-based controls to limit the domains from which images can be loaded within the application context. These targeted mitigations will reduce the risk of information disclosure while maintaining operational continuity until a permanent fix is applied.
Description
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.