# SUSE-SU-2025:20307-1: Security update for ca-certificates-mozilla

> Updates Mozilla root CA certificates in SUSE, removing untrusted CAs and adding new ones to maintain secure TLS validation.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 May 2025

## What is SUSE-SU-2025:20307-1?

SUSE-SU-2025:20307-1 is a vulnerability in ca-certificates-mozilla, published on 12 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This update for ca-certificates-mozilla fixes the following issues:

Update to 2.74 state of Mozilla SSL root CAs:

Removed:

* SwissSign Silver CA - G2

Added:

* D-TRUST BR Root CA 2 2023
* D-TRUST EV Root CA 2 2023

Updated to 2.72 state of Mozilla SSL root CAs (bsc#1234798):

Removed:

* SecureSign RootCA11
* Security Communication RootCA3

Added:

* TWCA CYBER Root CA
* TWCA Global Root CA G2
* SecureSign Root CA12
* SecureSign Root CA14
* SecureSign Root CA15

## Which versions are affected by SUSE-SU-2025:20307-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ca-certificates-mozilla` | SUSE:Linux Micro 6.1 | All versions | 2.74-slfo.1.1_1.1 |

## How do I fix SUSE-SU-2025:20307-1?

Upgrade to a fixed version.

## Is SUSE-SU-2025:20307-1 being exploited?

There is no known exploitation of SUSE-SU-2025:20307-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2025:20307-1 and fix it if it is affected.

What it is: SUSE-SU-2025:20307-1 is a vulnerability in ca-certificates-mozilla, published on 12 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2025:20307-1 in the wild and no public exploit code.

Affected product: ca-certificates-mozilla. 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/SUSE-SU-2025-20307-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2025-20307-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2025:20307-1

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