Snyk test report
- quay.io/argoproj/argocd:latest/argoproj/argocd/Dockerfile (deb)
- quay.io/argoproj/argocd:latest/argoproj/argo-cd/v3//usr/local/bin/argocd (gomodules)
- quay.io/argoproj/argocd:latest//usr/local/bin/git-lfs (gomodules)
- quay.io/argoproj/argocd:latest//usr/local/bin/kustomize (gomodules)
- quay.io/argoproj/argocd:latest/helm/v4//usr/local/bin/helm (gomodules)
- quay.io/argoproj/argocd:latest/canonical/pebble//usr/bin/pebble (gomodules)
Improper Check for Certificate Revocation
Detailed paths
Overview
std/crypto/x509 is a Go standard library package std/crypto/x509
Affected versions of this package are vulnerable to Improper Check for Certificate Revocation.
Go Vulnerability Report:
On most platforms, Go uses the given system root certificates. However, in some narrower cases, the system trust stores may not be updated without further action. To defend against the narrower set of cases that may remain affected, a denylist was added in crypto/x509 to return an error when calling Verify with any of the known intermediate certificates that are no longer considered to be trustworthy.
Remediation
Upgrade std/crypto/x509 to version 1.26.10, 1.27.3 or higher.
References
Denial of Service (DoS)
Detailed paths
Overview
std/crypto/tls is a Go standard library package std/crypto/tls
Affected versions of this package are vulnerable to Denial of Service (DoS).
Go Vulnerability Report:
Handshake messages, such as KeyUpdate, are always considered as state-advancing, regardless of whether a handshake has been completed or not. As a result, a malicious client can keep sending KeyUpdate messages to force the server to keep performing key derivation operations indefinitely.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
wspackage
Remediation
Upgrade std/crypto/tls to version 1.25.13, 1.26.6, 1.27.0-rc.3 or higher.
References
Uncontrolled Recursion
Detailed paths
Overview
std/encoding/asn1 is a Go standard library package std/encoding/asn1
Affected versions of this package are vulnerable to Uncontrolled Recursion.
Go Vulnerability Report:
Enforce a recursion limit in Unmarshal to prevent stack exhaustion when parsing deeply-nested, recursive structures.
Remediation
Upgrade std/encoding/asn1 to version 1.25.13, 1.26.6, 1.27.0-rc.3 or higher.
References
Uncontrolled Recursion
Detailed paths
Overview
std/encoding/xml is a Go standard library package std/encoding/xml
Affected versions of this package are vulnerable to Uncontrolled Recursion.
Go Vulnerability Report:
Previously, DecodeElement would reset the depth counter causing it to never fire; this could lead to stack exhaustion.
Remediation
Upgrade std/encoding/xml to version 1.25.13, 1.26.6, 1.27.0-rc.3 or higher.
References
Uncaught Exception
Detailed paths
Overview
std/net is a Go standard library package std/net
Affected versions of this package are vulnerable to Uncaught Exception.
Go Vulnerability Report:
Parsing an invalid SVCB or HTTPS RR can panic when the size of a parameter value overflows the message buffer.
Remediation
Upgrade std/net to version 1.26.6, 1.27.0-rc.3 or higher.
References
Denial of Service (DoS)
Detailed paths
Overview
std/net/http is a Go standard library package std/net/http
Affected versions of this package are vulnerable to Denial of Service (DoS).
Go Vulnerability Report:
When a server is configured to support unencrypted HTTP/2, it reads a few bytes from each new connection to see if they contain the HTTP/2 client preface. ReadHeaderTimeout is unexpectedly not being applied when doing this.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
wspackage
Remediation
Upgrade std/net/http to version 1.25.13, 1.26.6, 1.27.0-rc.3 or higher.
References
Denial of Service (DoS)
Detailed paths
Overview
std/net/url is a Go standard library package std/net/url
Affected versions of this package are vulnerable to Denial of Service (DoS).
Go Vulnerability Report:
Previously, resolving relative paths containing parent directory ('..') segments performed string conversions and buffer rewrites on each step, resulting in quadratic time complexity and high memory allocation overhead.Now, path resolution operates on a byte buffer using index-based backtracking for '..' segments, eliminating the quadratic time complexity and significantly reducing memory allocations.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
wspackage
Remediation
Upgrade std/net/url to version 1.25.13, 1.26.6, 1.27.0-rc.3 or higher.
References
Integer Overflow or Wraparound
Detailed paths
Overview
Affected versions of this package are vulnerable to Integer Overflow or Wraparound via the DecodeAll and streaming decoder process. An attacker can cause an application to crash by providing specially crafted zstd input that triggers a panic when processing two-block frames.
Remediation
Upgrade github.com/klauspost/compress/huff0 to version 1.20.2 or higher.
References
Integer Overflow or Wraparound
Detailed paths
Overview
Affected versions of this package are vulnerable to Integer Overflow or Wraparound via the DecodeAll and streaming decoder process. An attacker can cause an application to crash by providing specially crafted zstd input that triggers a panic when processing two-block frames.
Remediation
Upgrade github.com/klauspost/compress/fse to version 1.20.2 or higher.
References
Missing Release of File Descriptor or Handle after Effective Lifetime
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
The nsenter --join-cgroup option opens the target cgroup.procs file as root and leaves that file descriptor open across later namespace and credential changes and across execve(). Because the kernel checks later cgroup migrations using the credentials from the original open, a program run in an attacker-controlled target can inherit root's ability to move host processes between cgroups. After a privileged operator uses --join-cgroup against that target, an unprivileged user can migrate and terminate unrelated root processes.
Remediation
There is no fixed version for Ubuntu:26.04 util-linux.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-78408
- https://access.redhat.com/security/cve/CVE-2026-78408
- https://bugzilla.redhat.com/show_bug.cgi?id=2522497
- https://access.redhat.com/errata/RHSA-2026:63162
- http://www.openwall.com/lists/oss-security/2026/09/05/2
- https://access.redhat.com/errata/RHSA-2026:93461
- https://access.redhat.com/errata/RHSA-2026:95365
- https://github.com/util-linux/util-linux/security/advisories/GHSA-55fx-f4gg-cfhj
Link Following
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
A flaw was found in GNU tar. When extracting an archive with the --one-top-level option, hardlink targets are not confined to the designated top-level directory and may resolve relative to the extraction working directory. A crafted archive can create hardlinks that escape the intended boundary and, when combined with a preexisting symbolic link under the working directory, may allow writing outside that boundary during a single extraction.
Remediation
There is no fixed version for Ubuntu:26.04 tar.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-18508
- https://access.redhat.com/errata/RHSA-2026:50807
- https://access.redhat.com/security/cve/CVE-2026-18508
- https://bugzilla.redhat.com/show_bug.cgi?id=2509843
- https://access.redhat.com/errata/RHSA-2026:61581
- https://access.redhat.com/errata/RHSA-2026:61783
- https://access.redhat.com/errata/RHSA-2026:61586
- https://access.redhat.com/errata/RHSA-2026:66018
- https://access.redhat.com/errata/RHSA-2026:70390
Time-of-check Time-of-use (TOCTOU)
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
A TOCTOU (Time-of-Check Time-of-Use) vulnerability in GNU tar's incremental dumpdir 'X' rename handling allows a local attacker with write access to a directory being backed up to influence the restore process if the attacker has access to the system where the restore is being performed. During restoration, files or directories may be created, renamed or overwritten outside the intended extraction directory. This could lead to unauthorized file modification or, in some cases, privilege escalation. Exploitation does not require the attacker to modify or craft the archive, and standard backup and restore workflows—including extracting into a newly created directory without using the -P option do not mitigate the issue.
Remediation
There is no fixed version for Ubuntu:26.04 tar.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-18477
- https://access.redhat.com/errata/RHSA-2026:49361
- https://access.redhat.com/security/cve/CVE-2026-18477
- https://bugzilla.redhat.com/show_bug.cgi?id=2509735
- https://access.redhat.com/errata/RHSA-2026:61581
- https://access.redhat.com/errata/RHSA-2026:61783
- https://access.redhat.com/errata/RHSA-2026:61586
- https://access.redhat.com/errata/RHSA-2026:66018
- https://access.redhat.com/errata/RHSA-2026:70390
Exposure of Private Information ('Privacy Violation')
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
A flaw was found in the interaction between systemd-gpt-auto-generator and confidential computing guest VM images in OpenShift Sandboxed Containers (confidential peer pods). systemd-gpt-auto-generator automatically discovers and mounts GPT partitions by type GUID at boot with no user confirmation. In the confidential computing threat model, where the host/hypervisor is the adversary, a malicious host can inject partitions into the guest's virtual disk. Most critically, injecting a swap partition causes the guest kernel to page out TEE-encrypted memory to a host-controlled block device, breaking the confidentiality guarantee of the hardware TEE (AMD SEV-SNP, Intel TDX).
The PodVM images use a GPT-partitioned disk with dm-verity on the root partition. However, the roothash= kernel parameter only disables root auto-discovery — non-root partitions (swap, /home, /var, /srv, /var/tmp) are still auto-discovered and mounted. The generator is shipped unmasked in the RHEL systemd-udev subpackage, and no kernel command line parameter in the measured UKI addon disables it. Additionally, the PodVM measurement script captures PCRs 3, 9, 11, and 12, but not PCR 5 (GPT partition table), so partition table modifications are not detected by remote attestation.
Remediation
There is no fixed version for Ubuntu:26.04 systemd.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-121876
- https://access.redhat.com/security/cve/CVE-2026-121876
- https://bugzilla.redhat.com/show_bug.cgi?id=2558210
Cross-site Scripting (XSS)
Detailed paths
Overview
std/html/template is a Go standard library package std/html/template
Affected versions of this package are vulnerable to Cross-site Scripting (XSS).
Go Vulnerability Report:
Previously, pathological inputs could close an unescaped '/' early, allowing for attack-controlled data to inject arbitrary content, potentially leading to XSS.
Details
Cross-site scripting (or XSS) is a code vulnerability that occurs when an attacker “injects” a malicious script into an otherwise trusted website. The injected script gets downloaded and executed by the end user’s browser when the user interacts with the compromised website.
This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.
Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.
Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, < can be coded as < and > can be coded as > in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.
The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.
Types of attacks
There are a few methods by which XSS can be manipulated:
| Type | Origin | Description |
|---|---|---|
| Stored | Server | The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link. |
| Reflected | Server | The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser. |
| DOM-based | Client | The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data. |
| Mutated | The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters. |
Affected environments
The following environments are susceptible to an XSS attack:
- Web servers
- Application servers
- Web application environments
How to prevent
This section describes the top best practices designed to specifically protect your code:
- Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
- Convert special characters such as
?,&,/,<,>and spaces to their respective HTML or URL encoded equivalents. - Give users the option to disable client-side scripts.
- Redirect invalid requests.
- Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
- Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
- Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.
Remediation
Upgrade std/html/template to version 1.25.13, 1.26.6, 1.27.0-rc.3 or higher.
References
CVE-2026-35370
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
The id utility in uutils coreutils miscalculates the groups= section of its output. The implementation uses a user's real GID instead of their effective GID to compute the group list, leading to potentially divergent output compared to GNU coreutils. Because many scripts and automated processes rely on the output of id to make security-critical access-control or permission decisions, this discrepancy can lead to unauthorized access or security misconfigurations.
Remediation
There is no fixed version for Ubuntu:26.04 rust-coreutils.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-35370
- https://github.com/uutils/coreutils/issues/10006
CVE-2026-35371
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
The id utility in uutils coreutils exhibits incorrect behavior in its "pretty print" output when the real UID and effective UID differ. The implementation incorrectly uses the effective GID instead of the effective UID when performing a name lookup for the effective user. This results in misleading diagnostic output that can cause automated scripts or system administrators to make incorrect decisions regarding file permissions or access control.
Remediation
There is no fixed version for Ubuntu:26.04 rust-coreutils.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-35371
- https://github.com/uutils/coreutils/issues/10006
CVE-2026-35352
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream rust-coreutils package and not the rust-coreutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
A Time-of-Check to Time-of-Use (TOCTOU) race condition exists in the mkfifo utility of uutils coreutils. The utility creates a FIFO and then performs a path-based chmod to set permissions. A local attacker with write access to the parent directory can swap the newly created FIFO for a symbolic link between these two operations. This redirects the chmod call to an arbitrary file, potentially enabling privilege escalation if the utility is run with elevated privileges.
Remediation
There is no fixed version for Ubuntu:26.04 rust-coreutils.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-35352
- http://www.openwall.com/lists/oss-security/2026/05/04/4
- http://www.openwall.com/lists/oss-security/2026/05/04/5
- http://www.openwall.com/lists/oss-security/2026/05/04/6
- https://github.com/uutils/coreutils/issues/10020
CVE-2026-9538
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
Archive::Tar versions before 3.10 for Perl allow memory exhaustion via attacker controlled entry size field in tar header.
_read_tar() reads each entry's payload with $handle->read($$data, $block), where $block is derived from the entry's 12-byte size field in the tar header with no upper bound on that value.
A crafted header declaring a multi-gigabyte size causes Perl to allocate a scalar of that size.
Remediation
There is no fixed version for Ubuntu:26.04 perl.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-9538
- https://github.com/jib/archive-tar-new/commit/f9af01426038e29d9578825a0cd3626946ab08c7.patch
- https://metacpan.org/release/BINGOS/Archive-Tar-3.10/changes
- http://www.openwall.com/lists/oss-security/2026/05/26/4
Uncontrolled Recursion
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream p11-kit package and not the p11-kit package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
A flaw was found in p11-kit. The RPC message attribute parsing functions p11_rpc_message_get_attribute() and p11_rpc_message_get_attribute_array_value() form a mutually-recursive call chain with no recursion depth limit when processing nested CKA_WRAP_TEMPLATE, CKA_UNWRAP_TEMPLATE, and CKA_DERIVE_TEMPLATE attributes. An unauthenticated attacker with local access to the p11-kit RPC Unix domain socket can send a specially crafted request with deeply nested template attributes, causing stack exhaustion and crashing the p11-kit server process and its dependent services.
Remediation
There is no fixed version for Ubuntu:26.04 p11-kit.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-13757
- https://access.redhat.com/errata/RHSA-2026:37469
- https://access.redhat.com/errata/RHSA-2026:38342
- https://access.redhat.com/errata/RHSA-2026:49668
- https://access.redhat.com/security/cve/CVE-2026-13757
- https://bugzilla.redhat.com/show_bug.cgi?id=2494556
- https://github.com/advisories/GHSA-p2wm-69qx-x25w
- https://access.redhat.com/errata/RHSA-2026:49667
- https://access.redhat.com/errata/RHSA-2026:53371
- https://access.redhat.com/errata/RHSA-2026:54387
- https://access.redhat.com/errata/RHSA-2026:54760
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:72394
- https://access.redhat.com/errata/RHSA-2026:72395
- https://access.redhat.com/errata/RHSA-2026:72399
- https://access.redhat.com/errata/RHSA-2026:72470
- https://access.redhat.com/errata/RHSA-2026:72475
- https://access.redhat.com/errata/RHSA-2026:72476
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:81201
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82336
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
CVE-2026-110928
Detailed paths
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
There is no fixed version for Ubuntu:26.04 openssh.
References
CVE-2026-67693
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
GnuTLS v3.8.13 does not reject end-entity X.509 certificates that contain a contradictory combination of Key Usage (KU) and Extended Key Usage (EKU). NOTE: the Supplier does not consider this an actionable security vulnerability because of its "threat model doesn't consider attacks only possible by modifying anything within the trust boundary (private keys, trusted certificate authorities and their issued certificates including intermediate CAs, etc.)" policy.
Remediation
There is no fixed version for Ubuntu:26.04 gnutls28.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-67693
- http://gnutls.com
- https://gist.github.com/lkloliver/6fbfc191bc6163942c8017551ac3f238
- https://gitlab.com/gnutls/gnutls/-/blob/3.8.13/lib/x509/verify.c#L1119-1178
- https://gitlab.com/gnutls/gnutls/-/work_items/1642
- https://gitlab.com/gnutls/gnutls/-/blob/e2169a87c7fb91935c2845088204b102baed4c5f/SECURITY.md
- https://gitlab.com/gnutls/gnutls/-/work_items/1965
- https://github.com/lkloliver/poc/tree/main/CVE-2026-67693
CVE-2026-95209
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.
Remediation
There is no fixed version for Ubuntu:26.04 gnutls28.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-95209
- http://gnutls.com
- https://evil.com
- https://gist.github.com/lkloliver/8e4498311aff18e2077010e412043e18
- https://www.gnutls.org
CVE-2026-95184
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
GnuTLS v3.8.13 does not properly enforce name constraints, as demonstrated by a permitted subtree violation for "EE O=Evil accepted although outside permitted O=Good." NOTE: the Supplier does not consider this an actionable security vulnerability because of its "threat model doesn't consider attacks only possible by modifying anything within the trust boundary (private keys, trusted certificate authorities and their issued certificates including intermediate CAs, etc.)" policy.
Remediation
There is no fixed version for Ubuntu:26.04 gnutls28.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-95184
- http://gnutls.com
- https://evil.com
- https://gist.github.com/lkloliver/0c8b47fa75a0958fa88587665b82ae15
- https://www.gnutls.org
- https://gitlab.com/gnutls/gnutls/-/blob/e2169a87c7fb91935c2845088204b102baed4c5f/SECURITY.md
- https://gitlab.com/gnutls/gnutls/-/work_items/1965
- https://github.com/lkloliver/poc/tree/main/CVE-2026-95184
CVE-2026-88647
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
GnuTLS v3.8.13 can perhaps unexpectedly trust a certificate on the basis of Common Name when Subject Alternative Name has an SRV otherName (1.3.6.1.5.5.7.8.7) whose value is an OCTET STRING. NOTE: the Supplier does not consider this an actionable security vulnerability because of its "threat model doesn't consider attacks only possible by modifying anything within the trust boundary (private keys, trusted certificate authorities and their issued certificates including intermediate CAs, etc.)" policy.
Remediation
There is no fixed version for Ubuntu:26.04 gnutls28.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-88647
- https://gist.github.com/lkloliver/f98ec3de1a871fdfc02b70b8b9ba7642
- https://gitlab.com/gnutls/gnutls/-/issues/1802
- https://gitlab.com/gnutls/gnutls/-/blob/e2169a87c7fb91935c2845088204b102baed4c5f/SECURITY.md
- https://gitlab.com/gnutls/gnutls/-/work_items/1965
- https://github.com/lkloliver/poc/tree/main/CVE-2026-88647
CVE-2026-95210
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
GnuTLS v3.8.13 does not reject a critical keyUsage extension when it cannot be processed, such as when extnValue is an ASN.1 NULL (05 00) instead of a BIT STRING. NOTE: the Supplier does not consider this an actionable security vulnerability because of its "threat model doesn't consider attacks only possible by modifying anything within the trust boundary (private keys, trusted certificate authorities and their issued certificates including intermediate CAs, etc.)" policy.
Remediation
There is no fixed version for Ubuntu:26.04 gnutls28.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-95210
- http://gnutls.com
- https://gist.github.com/lkloliver/4aad23689202720c4068f43b3c6069c7
- https://gitlab.com/gnutls/gnutls/-/blob/e2169a87c7fb91935c2845088204b102baed4c5f/SECURITY.md
- https://gitlab.com/gnutls/gnutls/-/work_items/1965
- https://github.com/lkloliver/poc/tree/main/CVE-2026-95210
CVE-2026-88648
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
In GnuTLS v3.8.13, an excluded msUPN/SRV otherName is never checked. NOTE: the Supplier does not consider this an actionable security vulnerability because of its "threat model doesn't consider attacks only possible by modifying anything within the trust boundary (private keys, trusted certificate authorities and their issued certificates including intermediate CAs, etc.)" policy.
Remediation
There is no fixed version for Ubuntu:26.04 gnutls28.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-88648
- https://gist.github.com/lkloliver/1f2a97cb8d0b31aa27b6bd0354358d7d
- https://www.rfc-editor.org/rfc/rfc5280#section-4.2.1.10
- https://www.rfc-editor.org/rfc/rfc5280#section-6.1.4
- https://gitlab.com/gnutls/gnutls/-/blob/e2169a87c7fb91935c2845088204b102baed4c5f/SECURITY.md
- https://gitlab.com/gnutls/gnutls/-/work_items/1965
- https://github.com/lkloliver/poc/tree/main/CVE-2026-88648
CVE-2026-89092
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
The nscd service in the GNU C Library 2.3.4 onwards may crash due to a stack overflow when a malicious DNS server returns too large a response for a DNS query, resulting in degraded DNS resolution for the system.
Exploitation of this bug needs a system that has nscd enabled and using an untrusted DNS server for name resolution, with the compromised DNS server being capable of processing records large enough to result in a stack overflow in an nscd thread stack. During experimentation, bind 9 was unable to handle large records, but that could change in future or with a different name server. In typical installations, nscd is executed in an isolated context as its own user without a shell, due to which any compromise of that service is isolated.
There is a remote possibility of nscd cache corruption if an attacker manages to get the stack pointer into a desired point in the heap, potentially resulting in other caches in nscd being overwritten with corrupt data through the stack overflow, until the buggy code path eventually results in a crash.
Finally, a crash in nscd may result in performance degradation when resolving names, but it does not result in a denial of service.
Remediation
There is no fixed version for Ubuntu:26.04 glibc.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-89092
- https://sourceware.org/bugzilla/show_bug.cgi?id=34624
- https://sourceware.org/git/?p=glibc.git;a=blob_plain;f=advisories/GLIBC-SA-2026-0016
- http://www.openwall.com/lists/oss-security/2026/09/11/2
Improper Validation of Specified Type of Input
Detailed paths
Overview
Affected versions of this package are vulnerable to Improper Validation of Specified Type of Input in the calls plugin when handling websocket messages containing malformed msgpack frames. An attacker can cause the server to consume excessive memory and crash by sending specially crafted websocket requests.
Remediation
There is no fixed version for github.com/vmihailenco/msgpack/v5.
References
Incorrect Authorization
Detailed paths
Overview
Affected versions of this package are vulnerable to Incorrect Authorization in the ServeHTTP method of ServeMux (runtime/mux.go), which rewrites r.Method from the client-supplied X-HTTP-Method-Override header on form-urlencoded POST requests without restricting the allowed methods. An attacker can reach handlers for restricted verbs such as DELETE, PUT, or PATCH, bypassing method-based access controls enforced at an upstream proxy or WAF, by sending a POST request with Content-Type: application/x-www-form-urlencoded and the override header set to the target method. This requires a deployment where a perimeter proxy or WAF filters on the wire method while trusting the gateway downstream, and a handler must exist for the overridden method.
Note: The WithDisablePathLengthFallback is added in version 2.29.0 but it is disabled by default.
Workaround
This vulnerability can be avoided by stripping the X-HTTP-Method-Override header at the perimeter proxy or WAF, so the enforced wire method is the one the gateway routes on.
Remediation
Upgrade github.com/grpc-ecosystem/grpc-gateway/runtime to version 2.29.0 or higher.
References
Improper Encoding or Escaping of Output
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
Git is a source code management tool. When cloning from a server (or fetching, or pushing), informational or error messages are transported from the remote Git process to the client via the so-called "sideband channel". These messages will be prefixed with "remote:" and printed directly to the standard error output. Typically, this standard error output is connected to a terminal that understands ANSI escape sequences, which Git did not protect against. Most modern terminals support control sequences that can be used by a malicious actor to hide and misrepresent information, or to mislead the user into executing untrusted scripts. As requested on the git-security mailing list, the patches are under discussion on the public mailing list. Users are advised to update as soon as possible. Users unable to upgrade should avoid recursive clones unless they are from trusted sources.
Remediation
There is no fixed version for Ubuntu:26.04 git.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-52005
- https://github.com/git/git/security/advisories/GHSA-7jjc-gg6m-3329
- https://lore.kernel.org/git/1M9FnZ-1taoNo1wwh-00ESSd@mail.gmx.net
Algorithmic Complexity
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
In libexpat through 2.7.3, a crafted file with an approximate size of 2 MiB can lead to dozens of seconds of processing time.
Remediation
There is no fixed version for Ubuntu:26.04 expat.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-66382
- https://github.com/libexpat/libexpat/issues/1076
- http://www.openwall.com/lists/oss-security/2025/12/02/1
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html
Improper Handling of Unicode Encoding
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
Expat before 2.8.5 fails to validate that a high surrogate in UTF-16 input is followed by a low surrogate, allowing malformed UTF-16 sequences to be accepted. Attackers can supply UTF-16 encoded XML containing lone high surrogates that consume the following code unit, causing Expat to pass unpaired surrogates to applications built with XML_UNICODE and to silently replace input characters in other builds.
Remediation
There is no fixed version for Ubuntu:26.04 expat.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-93990
- https://github.com/libexpat/libexpat
- https://github.com/libexpat/libexpat/commit/ff6e1d7e750bbe245178f51a47a965dc8342861a
- https://github.com/libexpat/libexpat/pull/1282
- https://www.vulncheck.com/advisories/expat-through-2.8.4-malformed-utf-16-acceptance-via-unchecked-surrogate
- https://blog.hartwork.org/posts/expat-2-8-5-released/
- https://github.com/libexpat/libexpat/releases/tag/R_2_8_5
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
Integer Overflow or Wraparound
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
libexpat versions 2.7.2 through 2.8.5 contain an integer overflow vulnerability in expat_realloc() function on 32-bit platforms when computing allocation sizes. Attackers supplying malicious XML to applications parsing with vulnerable libexpat can cause heap buffer overflow, memory corruption, or denial of service.
Remediation
There is no fixed version for Ubuntu:26.04 expat.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-102633
- https://github.com/libexpat/libexpat
- https://github.com/libexpat/libexpat/blob/R_2_8_5/expat/lib/xmlparse.c#L1003
- https://github.com/libexpat/libexpat/commit/209801d7fbaf07ab74bae8cb32dd2ab9e5846118
- https://github.com/libexpat/libexpat/pull/1392
- https://www.vulncheck.com/advisories/libexpat-2.7.2-through-2.8.5-integer-overflow-in-expat-realloc
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
Inefficient Regular Expression Complexity
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream dash package and not the dash package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
A flaw was found in dash. When built without libc fnmatch, the internal pmatch() matcher implements * by unbounded recursion over candidate positions. A local user who can plant filenames, or otherwise feed that matcher, can make a short multi-star pattern such as ....*.tar.gz consume excessive CPU.
Remediation
There is no fixed version for Ubuntu:26.04 dash.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-102473
- https://access.redhat.com/security/cve/CVE-2026-102473
- https://bugzilla.redhat.com/show_bug.cgi?id=2543005
Out-of-bounds Write
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream dash package and not the dash package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
A flaw was found in dash. The printf builtin reserves four bytes before converting a Unicode \u or \U escape, but the multi-byte token can need five or six bytes. A local user who can supply such an escape to dash printf or echo %b, including through dash -c and a positional argument, can write one or two bytes past that reservation.
Remediation
There is no fixed version for Ubuntu:26.04 dash.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-102474
- https://access.redhat.com/security/cve/CVE-2026-102474
- https://bugzilla.redhat.com/show_bug.cgi?id=2543004
Heap-based Buffer Overflow
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream cyrus-sasl2 package and not the cyrus-sasl2 package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
A heap-based buffer overflow flaw was found in Cyrus SASL. The add_to_challenge() function in the DIGEST-MD5 plugin computes the size of the buffer needed for a challenge/response field before DIGEST-MD5 quoting is applied, but does not recompute that size when quoting (escaping special characters) makes the value longer. The under-sized buffer is then passed to strcat(), causing a heap-based out-of-bounds write whose size depends on attacker-controlled input. A malicious or on-path DIGEST-MD5 (or HTTP Digest) server can trigger this flaw in a connecting client by supplying a crafted challenge field, such as realm or nonce, most likely resulting in a crash of the client application.
Remediation
There is no fixed version for Ubuntu:26.04 cyrus-sasl2.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-107161
- https://access.redhat.com/security/cve/CVE-2026-107161
- https://bugzilla.redhat.com/show_bug.cgi?id=2460420
- http://www.openwall.com/lists/oss-security/2026/10/09/20
- https://lists.debian.org/debian-lts-announce/2026/10/msg00064.html
Incorrect Resource Transfer Between Spheres
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
In systemd 259, systemd-journald can send ANSI escape sequences to the terminals of arbitrary users when a "logger -p emerg" command is executed, if ForwardToWall=yes is set.
Remediation
There is no fixed version for Ubuntu:26.04 systemd.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-40228
- https://www.openwall.com/lists/oss-security/2026/04/08/1
- http://www.openwall.com/lists/oss-security/2026/05/05/1
CVE-2024-56433
Detailed paths
NVD Description
Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Ubuntu.
See How to fix? for Ubuntu:26.04 relevant fixed versions and status.
shadow-utils (aka shadow) 4.4 through 4.17.0 establishes a default /etc/subuid behavior (e.g., uid 100000 through 165535 for the first user account) that can realistically conflict with the uids of users defined on locally administered networks, potentially leading to account takeover, e.g., by leveraging newuidmap for access to an NFS home directory (or same-host resources in the case of remote logins by these local network users). NOTE: it may also be argued that system administrators should not have assigned uids, within local networks, that are within the range that can occur in /etc/subuid.
Remediation
There is no fixed version for Ubuntu:26.04 shadow.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-56433
- https://github.com/shadow-maint/shadow/blob/e2512d5741d4a44bdd81a8c2d0029b6222728cf0/etc/login.defs#L238-L241
- https://github.com/shadow-maint/shadow/issues/1157
- https://github.com/shadow-maint/shadow/releases/tag/4.4
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html