VulnerabilityPublished 26 Oct 2026

CVE-2026-56853: oci-seccomp-bpf-hook security update

Affects oci-seccomp-bpf-hookSource GCVE Database

Mentioned vulnerabilities

Authoritative record:CVE-2026-56853· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 1.2.11-3.el10_2 soon.

Data as of 26 Oct 2026, 23:30 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 1.2.11-3.el10_2

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

almalinux-10

What to do

Upgrade the AlmaLinux oci-seccomp-bpf-hook package to 1.2.11-3.el10_2.

Patches and advisories

access.redhat.com/errata/RHSA-2026:89752 (opens in a new tab)

Affected software

Product	Affected	Fixed in
AlmaLinux 10oci-seccomp-bpf-hook	Affected <1.2.11-3.el10_2	Fixed in 1.2.11-3.el10_2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A security update is available and should be applied. The fixed version is 1.2.11-3.el10_2 or later. Users should update oci-seccomp-bpf-hook to this version to remediate the vulnerabilities. Refer to the Red Hat advisory RHSA-2026:89752 and the update instructions at https://access.redhat.com/articles/11258 for detailed guidance.

Description

The oci-seccomp-bpf-hook library, used for generating seccomp JSON files for container syscall filtering, has a security update addressing multiple vulnerabilities in the Go net/http and crypto/x509 packages. One of these vulnerabilities (CVE-2026-56853) involves unencrypted HTTP/2 connections susceptible to denial of service attacks. The update fixes this and related issues, improving the security of container environments using this library.

Impact

Exploitation of CVE-2026-56853 can lead to denial of service conditions through unencrypted HTTP/2 connections. The other related vulnerabilities fixed in this update also pose risks of denial of service and man-in-the-middle attacks. These issues affect container environments relying on oci-seccomp-bpf-hook and underlying Go libraries, potentially impacting availability and confidentiality if exploited.

Summary

The oci-seccomp-bpf-hook component, which supports container pod concepts popularized by Kubernetes, was found vulnerable due to issues in underlying Go libraries. Specifically, CVE-2026-56853 describes a denial of service vulnerability via unencrypted HTTP/2 connections in the Go net/http package. This update also addresses other Go-related vulnerabilities including denial of service via crafted HTTP Range headers (CVE-2026-78667) and man-in-the-middle attacks via untrusted intermediate certificates in crypto/x509 (CVE-2026-111943). The Red Hat advisory confirms these fixes are included in version 1.2.11-3.el10_2 and later.

References

Community reviews

Loading reviews…