How severe is GHSA-hfcf-79gh-f3jc?

No CVSS score has been assigned to GHSA-hfcf-79gh-f3jc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hfcf-79gh-f3jc?

GHSA-hfcf-79gh-f3jc affects the following packages: github.com/usememos/memos (Go). Ecosystems affected: Go.

How do I fix GHSA-hfcf-79gh-f3jc?

Update github.com/usememos/memos to 0.24.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hfcf-79gh-f3jc is resolved across your whole dependency graph.

How do I detect GHSA-hfcf-79gh-f3jc in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/usememos/memos, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-hfcf-79gh-f3jc if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-hfcf-79gh-f3jc?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hfcf-79gh-f3jc can be triaged on real exposure rather than presence alone.

Is GHSA-hfcf-79gh-f3jc actively exploited in the wild?

No public exploit code has been indexed for GHSA-hfcf-79gh-f3jc yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-hfcf-79gh-f3jc?

GHSA-hfcf-79gh-f3jc has an EPSS (Exploit Prediction Scoring System) score of 2.1%, placing it in the 81th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-hfcf-79gh-f3jc?

GHSA-hfcf-79gh-f3jc is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-hfcf-79gh-f3jc published, and has it been updated?

GHSA-hfcf-79gh-f3jc was published on July 29, 2025 and was last updated on August 22, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-hfcf-79gh-f3jc: memos Info Disclosure

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-hfcf-79gh-f3jc.

EPSS Exploitation Probability

via FIRST.org ↗

2.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs81th percentile — riskier than 81% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐹github.com/usememos/memos

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/usememos/memos`	all versions	0.24.4`go get github.com/usememos/memos@v0.24.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/usememos/memos, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/usememos/memos to 0.24.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hfcf-79gh-f3jc is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hfcf-79gh-f3jc can be triaged on real exposure rather than presence alone.

Tailored to GHSA-hfcf-79gh-f3jc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-hfcf-79gh-f3jc in your dependencies?

O3 Security finds GHSA-hfcf-79gh-f3jc across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works

GHSA-hfcf-79gh-f3jc — memos