Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify internet-exposed Memos instance
-
DeliverySubmit crafted URL targeting 100.64.0.0/10 host
-
ExploitServer bypasses SSRF blocklist for CGNAT range
-
ExecutionServer fetches internal host metadata
-
ImpactAttacker receives page title and description
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the Memos instance's link-metadata fetcher is accessible to the attacker - either because the Memos deployment is internet-facing or because the attacker has network access to it. No authentication is required; the CVSS vector PR:N confirms unauthenticated access is sufficient. The critical environmental prerequisite is that internal hosts or services of interest must reside within the 100.64.0.0/10 CGNAT address range and be reachable from the Memos server's network interface. The impact is limited to reading HTML page titles and meta descriptions - not full response bodies, credentials, or file contents. Exploitation is not possible if the Memos server cannot reach any hosts in 100.64.0.0/10, or if egress filtering already blocks that range at the network layer. |
| Impact | The CVSS 4.0 score of 6.9 reflects a moderate, narrowly scoped confidentiality impact: the attacker receives page titles and HTML meta descriptions from CGNAT-addressed hosts, not full HTTP response bodies, limiting intelligence value. The attack surface is fully remote and unauthenticated (AV:N/AC:L/AT:N/PR:N/UI:N), making mass scanning of exposed Memos instances trivially automatable. Practical exploitability is highly environment-dependent: the 100.64.0.0/10 range is actionable only where internal services or sensitive infrastructure reside in that space. Importantly, the primary cloud hyperscalers (AWS, GCP, Azure) expose instance metadata at 169.254.169.254 (link-local), not in the CGNAT range, so standard cloud VM deployments may not expose metadata credentials through this specific vector - this is a meaningful limiting factor that the CVSS score does not capture. EPSS data was not provided in the available intelligence, and the absence of a KEV listing combined with no confirmed public exploit code suggests opportunistic exploitation is not yet observed. The VulnCheck advisory is the sole upstream source; no independent vendor patch confirmation is available, which introduces uncertainty about fix status. |
| Exploit ScenarioDerived | An unauthenticated attacker discovers a publicly accessible Memos instance and submits a crafted URL pointing to a host in the 100.64.0.0/10 range - for example, an internal API gateway or management interface reachable from the Memos server - to the link-preview or bookmark-creation feature. The Memos server fetches the URL, extracts the page title and meta description, and returns them to the attacker, revealing the name and partial content of internal services. No public proof-of-concept code has been identified, though the straightforward nature of the bypass (simply targeting the overlooked CGNAT range) means exploitation requires no specialized tooling. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 29, 2026
Server-side request forgery in Memos through 0.30.0 allows unauthenticated remote attackers to make the application's link-metadata fetcher issue HTTP requests to hosts in the 100.64.0.0/10 carrier-grade NAT address space, a range the application's IP blocklist incorrectly omits. The server returns page titles and HTML meta descriptions from targeted internal hosts, enabling partial reconnaissance of CGNAT-addressed infrastructure. No public exploit has been identified at time of analysis, and the vulnerability has not been added to the CISA KEV catalog.
RemediationAI
The primary remediation is to upgrade Memos beyond version 0.30.0 once a patched release is published; monitor the upstream repository at https://github.com/usememos/memos and the GitHub issue https://github.com/usememos/memos/issues/6099 for patch availability. No exact fix version has been confirmed in the available data. As a compensating control for internet-exposed instances, network-layer egress filtering should be applied to the host running Memos to block outbound HTTP/HTTPS requests to 100.64.0.0/10, in addition to the RFC 1918 ranges already implicitly blocked; this requires firewall or iptables rules at the OS level and does not require application changes, though it may break legitimate use cases if any link metadata targets reside in that range. Alternatively, restricting access to the Memos instance to authenticated internal users via a reverse proxy reduces the attack surface to trusted parties, trading public accessibility for reduced SSRF exposure.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability originates in Memos' HTML metadata fetcher, located at internal/httpgetter/html_meta.go (per the referenced source file at v0.30.0), which issues server-side HTTP requests to user-supplied URLs in order to extract Open Graph and HTML meta tags. The application applies SSRF protections by blocklisting known private address ranges but fails to include RFC 6598's 100.64.0.0/10 shared address space, originally allocated for carrier-grade NAT deployments and also used in some cloud provider overlay networks and private carrier routing fabrics. CWE-918 (Server-Side Request Forgery) is the root cause class: user-controlled input directly influences the destination of server-initiated requests without exhaustive address-space validation. The affected CPE is cpe:2.3:a:usememos:memos:*:*:*:*:*:*:*:* covering all releases through 0.30.0.
Know when Memos gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Network-reachable, no privileges, no interaction; scope changes as server fetches internal hosts; confidentiality limited to meta tag leakage only.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
Memos through 0.30.0 omits the 100.64.0.0/10 carrier-grade NAT address range from SSRF protection in its link-metadata fetcher, allowing unauthenticated attackers to bypass IP validation. Attackers can make the server request internal hosts in that range including cloud metadata services and read page titles and descriptions back.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
elestio memos v0.23.0 is vulnerable to Server-Side Request Forgery (SSRF) due to insufficient validation of user-supplie
Authorization Bypass Through User-Controlled Key in GitHub repository usememos/memos prior to 0.9.0. Rated critical seve
Cross-site Scripting (XSS) - Stored in GitHub repository usememos/memos prior to 0.9.1. Rated critical severity (CVSS 9.
Cross-site Scripting (XSS) - Stored in GitHub repository usememos/memos prior to 0.9.1. Rated critical severity (CVSS 9.
Cross-Site Request Forgery (CSRF) in GitHub repository usememos/memos prior to 0.15.1. Rated high severity (CVSS 8.8), t
Improper Privilege Management in GitHub repository usememos/memos prior to 0.13.2. Rated high severity (CVSS 8.8), this
Cross-Site Request Forgery (CSRF) in GitHub repository usememos/memos prior to 0.9.1. Rated high severity (CVSS 8.8), th
Improper Access Control in GitHub repository usememos/memos prior to 0.9.1. Rated high severity (CVSS 8.8), this vulnera
Improper Privilege Management in GitHub repository usememos/memos prior to 0.9.1. Rated high severity (CVSS 8.8), this v
Authorization Bypass Through User-Controlled Key in GitHub repository usememos/memos prior to 0.9.1. Rated high severity
Improper Access Control in GitHub repository usememos/memos prior to 0.9.0. Rated high severity (CVSS 8.8), this vulnera
Improper Authorization in GitHub repository usememos/memos prior to 0.9.0. Rated high severity (CVSS 8.8), this vulnerab
EUVD-2026-68132
GHSA-rw55-gcm9-cgjp
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB