De-anonymization via message

published 2021-07-15 5y ago modified 2026-06-17 4mo ago also EUVD-2021-19522

cvss: 6.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.8%; EPSS 0.8% chance of exploitation in 30 days, percentile 58%
public exploits: 0; none known

MuWire is a file publishing and networking tool that protects the identity of its users by using I2P technology. Users of MuWire desktop client prior to version 0.8.8 can be de-anonymized by an attacker who knows their full ID. An attacker could send a message with a subject line containing a URL with an HTML image tag and the MuWire client would try to fetch that image via clearnet, thus exposing the IP address of the user. The problem is fixed in MuWire 0.8.8. As a workaround, users can disable messaging functionality to prevent other users from sending them malicious messages.

Patch / fix

fixed in 1

muwire_project muwire 0.8.8

Is CVE-2021-32750 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.84% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

github.com https://github.com/zlatinb/muwire/security/advisories/GHSA-68xh-9h7w-64qg referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.8	CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N
NVD	3.1	5.7	CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
NVD	2.0	3.5	AV:N/AC:M/Au:S/C:P/I:N/A:N

Affected products

zlatinb muwire

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-79 Improper Neutralization of Input During Web Page Generation

References

github.com /zlatinb/muwire/security/advisories/GHSA-68xh-9h7w-64qg
exploit, third-party-advisory

Sources

CVE List CVE-2021-32750
NVD CVE-2021-32750

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

json all entries feed