# CVE-2025-69412: Security feature bypass in messagelib

> Attackers can spoof threat data by exploiting ignored SSL errors in the Google Safe Browsing API, requiring non-default configuration.

- **Severity:** Low 3.4 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Dec 2025
- **Updated:** 2 Jan 2026
- **Also known as:** DEBIAN-CVE-2025-69412, GHSA-q5rr-6j45-r8gx, OESA-2026-1039, OESA-2026-1040, OESA-2026-1041, OESA-2026-1042, UBUNTU-CVE-2025-69412

## What is CVE-2025-69412?

CVE-2025-69412 is a low-severity vulnerability in KDE messagelib, published on 31 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2025-69412?


## How do I fix CVE-2025-69412?

Upgrade to a fixed version.

## Is CVE-2025-69412 being exploited?

There is no known exploitation of CVE-2025-69412 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-69412 and fix it if it is affected.

What it is: CVE-2025-69412 is a low-severity vulnerability in KDE messagelib, published on 31 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-69412 in the wild and no public exploit code.

Affected product: KDE messagelib. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-69412/ (Markdown: https://insights.sbomify.com/CVE-2025-69412/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-69412
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-69412
- OSV: https://osv.dev/vulnerability/CVE-2025-69412

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-69412/
Summaries are generated and may contain mistakes; the official description above is the record.