SUSE-SU-2025:20565-1
Vulnerability from csaf_suse - Published: 2025-08-21 08:01 - Updated: 2026-11-15 17:23| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: SUSE Linux Micro 6.0:docker-0:28.3.3_ce-6.1.aarch64 | — |
Vendor Fix
|
|
| Unresolved product id: SUSE Linux Micro 6.0:docker-0:28.3.3_ce-6.1.s390x | — |
Vendor Fix
|
|
| Unresolved product id: SUSE Linux Micro 6.0:docker-0:28.3.3_ce-6.1.x86_64 | — |
Vendor Fix
|
|
| Unresolved product id: SUSE Linux Micro 6.0:docker-buildx-0:0.26.1-6.1.aarch64 | — |
Vendor Fix
|
|
| Unresolved product id: SUSE Linux Micro 6.0:docker-buildx-0:0.26.1-6.1.s390x | — |
Vendor Fix
|
|
| Unresolved product id: SUSE Linux Micro 6.0:docker-buildx-0:0.26.1-6.1.x86_64 | — |
Vendor Fix
|
{
"document": {
"aggregate_severity": {
"namespace": "https://www.suse.com/support/security/rating/",
"text": "moderate"
},
"category": "csaf_security_advisory",
"csaf_version": "2.0",
"distribution": {
"text": "Copyright 2024 SUSE LLC. All rights reserved.",
"tlp": {
"label": "WHITE",
"url": "https://www.first.org/tlp/"
}
},
"lang": "en",
"notes": [
{
"category": "summary",
"text": "Security update for docker",
"title": "Title of the patch"
},
{
"category": "description",
"text": "This update for docker fixes the following issues:\n\n- Update to Docker 28.3.3-ce: \n * CVE-2025-54388: firewalld reload can make published container \n ports accessible from remote hosts (bsc#1247367)\n\n- Update to docker-buildx v0.26.1.\n",
"title": "Description of the patch"
},
{
"category": "details",
"text": "SUSE-SLE-Micro-6.0-430",
"title": "Patchnames"
},
{
"category": "legal_disclaimer",
"text": "CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).",
"title": "Terms of use"
}
],
"publisher": {
"category": "vendor",
"contact_details": "https://www.suse.com/support/security/contact/",
"name": "SUSE Product Security Team",
"namespace": "https://www.suse.com/"
},
"references": [
{
"category": "external",
"summary": "SUSE ratings",
"url": "https://www.suse.com/support/security/rating/"
},
{
"category": "self",
"summary": "URL of this CSAF notice",
"url": "https://ftp.suse.com/pub/projects/security/csaf/2025/suse-su-2025_20565-1.json"
},
{
"category": "self",
"summary": "URL for SUSE-SU-2025:20565-1",
"url": "https://www.suse.com/support/update/announcement/2025/suse-su-202520565-1/"
},
{
"category": "self",
"summary": "E-Mail link for SUSE-SU-2025:20565-1",
"url": "https://lists.suse.com/pipermail/sle-security-updates/2025-August/022314.html"
},
{
"category": "self",
"summary": "SUSE Bug 1247367",
"url": "https://bugzilla.suse.com/1247367"
},
{
"category": "self",
"summary": "SUSE CVE CVE-2025-54388 page",
"url": "https://www.suse.com/security/cve/CVE-2025-54388/"
}
],
"title": "Security update for docker",
"tracking": {
"current_release_date": "2026-11-15T17:23:08Z",
"generator": {
"date": "2025-08-21T08:01:27Z",
"engine": {
"name": "cve-database.git:bin/generate-csaf.pl",
"version": "1"
}
},
"id": "SUSE-SU-2025:20565-1",
"initial_release_date": "2025-08-21T08:01:27Z",
"revision_history": [
{
"date": "2025-08-21T08:01:27Z",
"number": "1",
"summary": "Current version"
},
{
"date": "2026-09-20T18:14:47Z",
"number": "2",
"summary": "unknown changes"
},
{
"date": "2026-11-15T17:23:08Z",
"number": "3",
"summary": "unknown changes"
}
],
"status": "final",
"version": "3"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_version",
"name": "docker-0:28.3.3_ce-6.1.aarch64",
"product": {
"name": "docker-0:28.3.3_ce-6.1.aarch64",
"product_id": "docker-0:28.3.3_ce-6.1.aarch64",
"product_identification_helper": {
"cpe": "cpe:2.3:a:mobyproject:moby:28.3.3_ce:*:*:*:*:*:*:*",
"purl": "pkg:rpm/suse/docker@28.3.3_ce-6.1?arch=aarch64\u0026upstream=docker-0:28.3.3_ce-6.1.src.rpm"
}
}
},
{
"category": "product_version",
"name": "docker-buildx-0:0.26.1-6.1.aarch64",
"product": {
"name": "docker-buildx-0:0.26.1-6.1.aarch64",
"product_id": "docker-buildx-0:0.26.1-6.1.aarch64",
"product_identification_helper": {
"cpe": "cpe:2.3:a:mobyproject:moby:0.26.1:*:*:*:*:*:*:*",
"purl": "pkg:rpm/suse/docker-buildx@0.26.1-6.1?arch=aarch64\u0026upstream=docker-0:0.26.1-6.1.src.rpm"
}
}
}
],
"category": "architecture",
"name": "aarch64"
},
{
"branches": [
{
"category": "product_version",
"name": "docker-0:28.3.3_ce-6.1.s390x",
"product": {
"name": "docker-0:28.3.3_ce-6.1.s390x",
"product_id": "docker-0:28.3.3_ce-6.1.s390x",
"product_identification_helper": {
"cpe": "cpe:2.3:a:mobyproject:moby:28.3.3_ce:*:*:*:*:*:*:*",
"purl": "pkg:rpm/suse/docker@28.3.3_ce-6.1?arch=s390x\u0026upstream=docker-0:28.3.3_ce-6.1.src.rpm"
}
}
},
{
"category": "product_version",
"name": "docker-buildx-0:0.26.1-6.1.s390x",
"product": {
"name": "docker-buildx-0:0.26.1-6.1.s390x",
"product_id": "docker-buildx-0:0.26.1-6.1.s390x",
"product_identification_helper": {
"cpe": "cpe:2.3:a:mobyproject:moby:0.26.1:*:*:*:*:*:*:*",
"purl": "pkg:rpm/suse/docker-buildx@0.26.1-6.1?arch=s390x\u0026upstream=docker-0:0.26.1-6.1.src.rpm"
}
}
}
],
"category": "architecture",
"name": "s390x"
},
{
"branches": [
{
"category": "product_version",
"name": "docker-0:28.3.3_ce-6.1.x86_64",
"product": {
"name": "docker-0:28.3.3_ce-6.1.x86_64",
"product_id": "docker-0:28.3.3_ce-6.1.x86_64",
"product_identification_helper": {
"cpe": "cpe:2.3:a:mobyproject:moby:28.3.3_ce:*:*:*:*:*:*:*",
"purl": "pkg:rpm/suse/docker@28.3.3_ce-6.1?arch=x86_64\u0026upstream=docker-0:28.3.3_ce-6.1.src.rpm"
}
}
},
{
"category": "product_version",
"name": "docker-buildx-0:0.26.1-6.1.x86_64",
"product": {
"name": "docker-buildx-0:0.26.1-6.1.x86_64",
"product_id": "docker-buildx-0:0.26.1-6.1.x86_64",
"product_identification_helper": {
"cpe": "cpe:2.3:a:mobyproject:moby:0.26.1:*:*:*:*:*:*:*",
"purl": "pkg:rpm/suse/docker-buildx@0.26.1-6.1?arch=x86_64\u0026upstream=docker-0:0.26.1-6.1.src.rpm"
}
}
}
],
"category": "architecture",
"name": "x86_64"
},
{
"branches": [
{
"category": "product_name",
"name": "SUSE Linux Micro 6.0",
"product": {
"name": "SUSE Linux Micro 6.0",
"product_id": "SUSE Linux Micro 6.0",
"product_identification_helper": {
"cpe": "cpe:/o:suse:sl-micro:6.0"
}
}
}
],
"category": "product_family",
"name": "SUSE Linux Enterprise"
}
],
"category": "vendor",
"name": "SUSE"
}
],
"relationships": [
{
"category": "default_component_of",
"full_product_name": {
"name": "docker-0:28.3.3_ce-6.1.aarch64 as component of SUSE Linux Micro 6.0",
"product_id": "SUSE Linux Micro 6.0:docker-0:28.3.3_ce-6.1.aarch64"
},
"product_reference": "docker-0:28.3.3_ce-6.1.aarch64",
"relates_to_product_reference": "SUSE Linux Micro 6.0"
},
{
"category": "default_component_of",
"full_product_name": {
"name": "docker-0:28.3.3_ce-6.1.s390x as component of SUSE Linux Micro 6.0",
"product_id": "SUSE Linux Micro 6.0:docker-0:28.3.3_ce-6.1.s390x"
},
"product_reference": "docker-0:28.3.3_ce-6.1.s390x",
"relates_to_product_reference": "SUSE Linux Micro 6.0"
},
{
"category": "default_component_of",
"full_product_name": {
"name": "docker-0:28.3.3_ce-6.1.x86_64 as component of SUSE Linux Micro 6.0",
"product_id": "SUSE Linux Micro 6.0:docker-0:28.3.3_ce-6.1.x86_64"
},
"product_reference": "docker-0:28.3.3_ce-6.1.x86_64",
"relates_to_product_reference": "SUSE Linux Micro 6.0"
},
{
"category": "default_component_of",
"full_product_name": {
"name": "docker-buildx-0:0.26.1-6.1.aarch64 as component of SUSE Linux Micro 6.0",
"product_id": "SUSE Linux Micro 6.0:docker-buildx-0:0.26.1-6.1.aarch64"
},
"product_reference": "docker-buildx-0:0.26.1-6.1.aarch64",
"relates_to_product_reference": "SUSE Linux Micro 6.0"
},
{
"category": "default_component_of",
"full_product_name": {
"name": "docker-buildx-0:0.26.1-6.1.s390x as component of SUSE Linux Micro 6.0",
"product_id": "SUSE Linux Micro 6.0:docker-buildx-0:0.26.1-6.1.s390x"
},
"product_reference": "docker-buildx-0:0.26.1-6.1.s390x",
"relates_to_product_reference": "SUSE Linux Micro 6.0"
},
{
"category": "default_component_of",
"full_product_name": {
"name": "docker-buildx-0:0.26.1-6.1.x86_64 as component of SUSE Linux Micro 6.0",
"product_id": "SUSE Linux Micro 6.0:docker-buildx-0:0.26.1-6.1.x86_64"
},
"product_reference": "docker-buildx-0:0.26.1-6.1.x86_64",
"relates_to_product_reference": "SUSE Linux Micro 6.0"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2025-54388",
"ids": [
{
"system_name": "SUSE CVE Page",
"text": "https://www.suse.com/security/cve/CVE-2025-54388"
}
],
"notes": [
{
"category": "general",
"text": "Moby is an open source container framework developed by Docker Inc. that is distributed as Docker Engine, Mirantis Container Runtime, and various other downstream projects/products. In versions 28.2.0 through 28.3.2, when the firewalld service is reloaded it removes all iptables rules including those created by Docker. While Docker should automatically recreate these rules, versions before 28.3.3 fail to recreate the specific rules that block external access to containers. This means that after a firewalld reload, containers with ports published to localhost (like 127.0.0.1:8080) become accessible from remote machines that have network routing to the Docker bridge, even though they should only be accessible from the host itself. The vulnerability only affects explicitly published ports - unpublished ports remain protected. This issue is fixed in version 28.3.3.",
"title": "CVE description"
}
],
"product_status": {
"recommended": [
"SUSE Linux Micro 6.0:docker-0:28.3.3_ce-6.1.aarch64",
"SUSE Linux Micro 6.0:docker-0:28.3.3_ce-6.1.s390x",
"SUSE Linux Micro 6.0:docker-0:28.3.3_ce-6.1.x86_64",
"SUSE Linux Micro 6.0:docker-buildx-0:0.26.1-6.1.aarch64",
"SUSE Linux Micro 6.0:docker-buildx-0:0.26.1-6.1.s390x",
"SUSE Linux Micro 6.0:docker-buildx-0:0.26.1-6.1.x86_64"
]
},
"references": [
{
"category": "external",
"summary": "CVE-2025-54388",
"url": "https://www.suse.com/security/cve/CVE-2025-54388"
},
{
"category": "external",
"summary": "SUSE Bug 1247367 for CVE-2025-54388",
"url": "https://bugzilla.suse.com/1247367"
},
{
"category": "external",
"summary": "SUSE Bug 1265255 for CVE-2025-54388",
"url": "https://bugzilla.suse.com/1265255"
},
{
"category": "external",
"summary": "SUSE Bug 1265256 for CVE-2025-54388",
"url": "https://bugzilla.suse.com/1265256"
},
{
"category": "external",
"summary": "SUSE Bug 1265259 for CVE-2025-54388",
"url": "https://bugzilla.suse.com/1265259"
}
],
"remediations": [
{
"category": "vendor_fix",
"details": "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n",
"product_ids": [
"SUSE Linux Micro 6.0:docker-0:28.3.3_ce-6.1.aarch64",
"SUSE Linux Micro 6.0:docker-0:28.3.3_ce-6.1.s390x",
"SUSE Linux Micro 6.0:docker-0:28.3.3_ce-6.1.x86_64",
"SUSE Linux Micro 6.0:docker-buildx-0:0.26.1-6.1.aarch64",
"SUSE Linux Micro 6.0:docker-buildx-0:0.26.1-6.1.s390x",
"SUSE Linux Micro 6.0:docker-buildx-0:0.26.1-6.1.x86_64"
]
}
],
"scores": [
{
"cvss_v3": {
"baseScore": 5.2,
"baseSeverity": "MEDIUM",
"vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"products": [
"SUSE Linux Micro 6.0:docker-0:28.3.3_ce-6.1.aarch64",
"SUSE Linux Micro 6.0:docker-0:28.3.3_ce-6.1.s390x",
"SUSE Linux Micro 6.0:docker-0:28.3.3_ce-6.1.x86_64",
"SUSE Linux Micro 6.0:docker-buildx-0:0.26.1-6.1.aarch64",
"SUSE Linux Micro 6.0:docker-buildx-0:0.26.1-6.1.s390x",
"SUSE Linux Micro 6.0:docker-buildx-0:0.26.1-6.1.x86_64"
]
}
],
"threats": [
{
"category": "impact",
"date": "2025-08-21T08:01:27Z",
"details": "moderate"
}
],
"title": "CVE-2025-54388"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.