CVE-2026-115538 json
Docker Engine overlay-network encryption rules are not restored after a firewalld reload
published yesterday modified yesterday also EUVD-2026-122881 , GHSA-6jhp-7446-hf7f
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository moby/moby. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 7.0
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
Moby's overlay network driver does not restore the iptables rules for encrypted overlay networks after firewalld deletes them. Unlike other Docker Engine networking components, the overlay driver does not handle firewalld reload or start signals over D-Bus. The missing rules cause outgoing VXLAN datagrams to bypass IPsec encryption and remove the protection against incoming cleartext VXLAN traffic. The condition is not logged by dockerd and persists until the encrypted network's last local endpoint is removed and another is added, or dockerd is restarted. Each further firewalld event repeats the condition.
Patch / fix
- go github.com/moby/moby/v2 v2.0.0-beta.29
- Docker Docker Engine 29.9.3
- Moby Moby v2.0.0-beta.29
- docker Alpine 3.24 29.9.3-r0
alpine advisories ALPINE-CVE-2026-115538
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Is CVE-2026-115538 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.0 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:L |
| CNA | 4.0 | 7.0 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/moby/moby/v2 | <=v2.0.0-beta.28 |
v2.0.0-beta.29 |
Affected products
- Docker Docker Engine
- Moby Moby
Classification
- Weakness
-
- CWE-693 Protection Mechanism Failure
- Technology feeds
References
-
github.com
/moby/moby/security/advisories/GHSA-6jhp-7446-hf7f
vendor-advisory, advisory
Sources
- CVE List CVE-2026-115538
- NVD CVE-2026-115538
- Maintainer advisory GHSA-6jhp-7446-hf7f
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of moby/moby published their own advisory on GitHub. Reviewed sources take precedence over it.