# GitLab Patch Release: 18.8.2, 18.7.2, 18.6.4

Source: [https://about.gitlab.com/releases/2026/01/21/patch-release-gitlab-18-8-2-released/](https://about.gitlab.com/releases/2026/01/21/patch-release-gitlab-18-8-2-released/)

Learn more about GitLab Patch Release: 18.8.2, 18.7.2, 18.6.4 for GitLab Community Edition (CE) and Enterprise Edition (EE).

Today, we are releasing versions 18.8.2, 18.7.2, 18.6.4 for GitLab Community Edition (CE) and Enterprise Edition (EE).

These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action.

GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch releases: scheduled releases and ad-hoc critical patches for high-severity vulnerabilities. Scheduled releases are released twice a month on the second and fourth Wednesdays. For more information, please visit our [releases handbook](https://handbook.gitlab.com/handbook/engineering/releases/) and [security FAQ](https://about.gitlab.com/security/faq/). You can see all of GitLab release blog posts [here](https://about.gitlab.com/releases/categories/releases/).

For security fixes, the issues detailing each vulnerability are made public on our [issue tracker](https://gitlab.com/gitlab-org/gitlab/-/issues/?sort=created_date&state=closed&label_name%5B%5D=bug%3A%3Avulnerability&confidential=no&first_page_size=100) 30 days after the release in which they were patched.

We are committed to ensuring that all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. To maintain good security hygiene, it is highly recommended that all customers upgrade to the latest patch release for their supported version. You can read more [best practices in securing your GitLab instance](https://about.gitlab.com/blog/2020/05/20/gitlab-instance-security-best-practices/) in our blog post.

### Recommended Action

We **strongly recommend** that all installations running a version affected by the issues described below are **upgraded to the latest version as soon as possible**.

When no specific deployment type (omnibus, source code, helm chart, etc.) of a product is mentioned, it means all types are affected.

Security fixes
--------------

### Table of security fixes

|Title                                                                       |Severity|
|----------------------------------------------------------------------------|--------|
|Denial of Service issue in in Jira Connect integration impacts GitLab CE/EE |High    |
|Incorrect Authorization issue in Releases API impacts GitLab CE/EE          |High    |
|Unchecked Return Value issue in authentication services impacts GitLab CE/EE|High    |
|Infinite Loop issue in Wiki redirects impacts GitLab CE/EE                  |Medium  |
|Denial of Service issue in API endpoint impacts GitLab CE/EE                |Medium  |

### [CVE-2025-13927](https://www.cve.org/CVERecord?id=CVE-2025-13927) - Denial of Service issue in Jira Connect integration impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed an unauthenticated user to create a denial of service condition by sending crafted requests with malformed authentication data.

**Impacted Versions:** GitLab CE/EE: all versions from 11.9 before 18.6.4, 18.7 before 18.7.2, and 18.8 before 18.8.2
**CVSS** 7.5 ([`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`](https://gitlab-com.gitlab.io/gl-security/product-security/appsec/cvss-calculator/explain#explain=CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H))

Thanks [a92847865](https://hackerone.com/a92847865) for reporting this vulnerability through our HackerOne bug bounty program.

### [CVE-2025-13928](https://www.cve.org/CVERecord?id=CVE-2025-13928) - Incorrect Authorization issue in Releases API impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed an unauthenticated user to cause a denial of service condition by exploiting incorrect authorization validation in API endpoints.

**Impacted Versions:** GitLab CE/EE: all versions from 17.7 before 18.6.4, 18.7 before 18.7.2, and 18.8 before 18.8.2
**CVSS** 7.5 ([`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`](https://gitlab-com.gitlab.io/gl-security/product-security/appsec/cvss-calculator/explain#explain=CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H))

Thanks [a92847865](https://hackerone.com/a92847865) for reporting this vulnerability through our HackerOne bug bounty program.

### [CVE-2026-0723](https://www.cve.org/CVERecord?id=CVE-2026-0723) - Unchecked Return Value issue in authentication services impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed an individual with existing knowledge of a victim's credential ID to bypass two-factor authentication by submitting forged device responses.

**Impacted Versions:** GitLab CE/EE: all versions from 18.6 before 18.6.4, 18.7 before 18.7.2, and 18.8 before 18.8.2
**CVSS** 7.4 ([`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`](https://gitlab-com.gitlab.io/gl-security/product-security/appsec/cvss-calculator/explain#explain=CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N))

Thanks [ahacker1](https://hackerone.com/ahacker1) for reporting this vulnerability through our HackerOne bug bounty program.

### [CVE-2025-13335](https://www.cve.org/CVERecord?id=CVE-2025-13335) - Infinite Loop issue in Wiki redirects impacts GitLab CE/EE

GitLab has remediated an issue that under certain circumstances could have allowed an authenticated user to create a denial of service condition by configuring malformed Wiki documents that bypass cycle detection.

**Impacted Versions:** GitLab CE/EE: all versions from 17.1 before 18.6.4, 18.7 before 18.7.2, and 18.8 before 18.8.2
**CVSS** 6.5 ([`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`](https://gitlab-com.gitlab.io/gl-security/product-security/appsec/cvss-calculator/explain#explain=CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H))

Thanks [sim4n6](https://hackerone.com/sim4n6) for reporting this vulnerability through our HackerOne bug bounty program.

### [CVE-2026-1102](https://www.cve.org/CVERecord?id=CVE-2026-1102) - Denial of Service issue in API endpoint impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed an unauthenticated user to create a denial of service condition by sending repeated malformed SSH authentication requests.

**Impacted Versions:** GitLab CE/EE: all versions from 12.3 before 18.6.4, 18.7 before 18.7.2, and 18.8 before 18.8.2
**CVSS** 5.3 ([`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`](https://gitlab-com.gitlab.io/gl-security/product-security/appsec/cvss-calculator/explain#explain=CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L))

This vulnerability has been discovered internally by GitLab team member [Thiago Figueiró](https://gitlab.com/thiagocsf).

Bug fixes
---------

### 18.8.2

*   [Backport of `Make external agent configurations GA`](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/219214)
*   [Backport Remove GitLab Dedicated support for semantic search until it's available](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/219155)
*   [Backport of '18.8.0: Merge Request reviewer dropdown crashes and does not send request'](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/219235)
*   [Backport of 'Pass user id to workflow service'](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/219349)
*   [Backport of rake task to seed AI Catalogs with external agents](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/219380)
*   [Backport of `Separate policy logic for AI Catalog Flows and Foundational Flows`](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/219447)

### 18.7.2

*   [Backport of `Fix logic for fetching occurrences related to vulnerabilties`](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/216906)
*   [Backport of "Removes feature flag enablement for svc accounts"](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/217917)
*   [Backport of flaky import spec quarantine](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/217509)
*   [Backport 18.7 - Fix searchable dropdown race condition when typing fast](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/217840)
*   [Backport of `Recreate p_sent_notifications.reply_key index`](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/218037)
*   [Fix container\_repositories index repair to handle 1-to-1 relationship](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/217768)
*   [\[18.7\] Fix migration health check endpoint](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/218128)
*   [Backport of 'Fix soft wrap not working due to accessibilitySupport conflict'](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/218571)
*   [Backport of 'Fix git push error for remote flows in self-managed instances'](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/217993)
*   [\[Backport 18.7\] Exclude Git LFS paths from Git HTTP throttling](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/218752)
*   [Backport of `Correct Code Review Flow history for beta`](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/218940)
*   [Backport of 'Fix Duo Chat button visibility for Amazon Q'](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/218683)
*   [Backport Allow user namespaces to be indexed in Zoekt for self-managed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/218904)
*   [Backport of 'Disable Sidekiq retries for ClickHouse pipeline/build sync workers'](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/219407)
*   [Backport of 'Disable async\_insert in build and pipeline sync operations'](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/219445)
*   [18.7 - Remove manual from SLES-12.5-release-pulp job](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/8986)

### 18.6.4

*   [Backport of "Removes feature flag enablement for svc accounts"](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/217919)
*   [Backport of flaky import spec quarantine](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/217510)
*   [Backport 18.6 - Fix searchable dropdown race condition when typing fast](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/217841)
*   [Fix container\_repositories index repair to handle 1-to-1 relationship](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/217769)
*   [Backport of 'Fix soft wrap not working due to accessibilitySupport conflict'](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/218625)
*   [Backport of 'Fix git push error for remote flows in self-managed instances'](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/218021)
*   [\[Backport 18.6\] Exclude Git LFS paths from Git HTTP throttling](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/218750)
*   [Backport-Allow user namespaces to be indexed in Zoekt for self-managed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/218907)
*   [Backport of 'Disable Sidekiq retries for ClickHouse pipeline/build sync workers'](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/219406)
*   [Backport of 'Disable async\_insert in build and pipeline sync operations'](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/219444)
*   [18.6 - Remove manual from SLES-12.5-release-pulp job](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/8987)
*   [Start Pulp FIPS jobs after PC FIPS jobs - 18.6](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/9019)
*   [\[CI\] Fix the builder image tags for the check-packages jobs 18-6](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/8974)

Important notes on upgrading
----------------------------

This patch includes database migrations that may impact your upgrade process.

### Impact on your installation:

*   **Single-node instances**: This patch will cause downtime during the upgrade as migrations must complete before GitLab can start.
*   **Multi-node instances**: With proper [zero-downtime upgrade procedures](https://docs.gitlab.com/ee/update/zero_downtime.html), this patch can be applied without downtime.

### Post-deploy migrations

The following versions include post-deploy migrations that can run after the upgrade:

*   18.7.2

To learn more about the impact of upgrades on your installation, see:

*   [Zero-downtime upgrades](https://docs.gitlab.com/ee/update/zero_downtime.html) for multi-node deployments
*   [Standard upgrades](https://docs.gitlab.com/update/package/#downtime) for single-node installations

Updating
--------

To update GitLab, see the [Update page](https://about.gitlab.com/update). To update GitLab Runner, see the [Updating the Runner page](https://docs.gitlab.com/runner/install/linux-repository.html#updating-the-runner).

Receive Patch Notifications
---------------------------

To receive patch blog notifications delivered to your inbox, visit our [contact us](https://about.gitlab.com/company/contact/) page. To receive release notifications via RSS, subscribe to our [patch release RSS feed](https://about.gitlab.com/security-releases.xml) or our [RSS feed for all releases](https://about.gitlab.com/all-releases.xml).


The GNU C Library version 2.43 is now available

Security related changes:

The following CVEs were fixed in this release, details of which can be
found in the advisories directory of the release tarball:

  GLIBC-SA-2026-0001:
    Integer overflow in memalign leads to heap corruption
    (CVE-2026-0861)

  GLIBC-SA-2026-0002:
    getnetbyaddr and getnetbyaddr_r leak stack contents to DNS resovler
    (CVE-2026-0915)

  GLIBC-SA-2026-0003:
    wordexp with WRDE_REUSE and WRDE_APPEND may return uninitialized
    memory (CVE-2025-15281)

For more details: [https://lists.gnu.org/archive/html/info-gnu/2026-01/msg00005.html](https://lists.gnu.org/archive/html/info-gnu/2026-01/msg00005.html)


Vulnerabilities in multiple telnet implementation

A similar vulnerability was introduced three times on three different code base (AIX, Solaris and GNU) in three different decades (1993, 2004 and 2014).


# OpenSSL Security Advisory [27th January 2026]

Improper validation of PBMAC1 parameters in PKCS#12 MAC verification (CVE-2025-11187)
=====================================================================================

Severity: Moderate

Issue summary: PBMAC1 parameters in PKCS#12 files are missing validation
which can trigger a stack-based buffer overflow, invalid pointer or NULL
pointer dereference during MAC verification.

Impact summary: The stack buffer overflow or NULL pointer dereference may
cause a crash leading to Denial of Service for an application that parses
untrusted PKCS#12 files. The buffer overflow may also potentially enable
code execution depending on platform mitigations.

When verifying a PKCS#12 file that uses PBMAC1 for the MAC, the PBKDF2
salt and keylength parameters from the file are used without validation.
If the value of keylength exceeds the size of the fixed stack buffer used
for the derived key (64 bytes), the key derivation will overflow the buffer.
The overflow length is attacker-controlled. Also, if the salt parameter is
not an OCTET STRING type this can lead to invalid or NULL pointer
dereference.

Exploiting this issue requires a user or application to process
a maliciously crafted PKCS#12 file. It is uncommon to accept untrusted
PKCS#12 files in applications as they are usually used to store private
keys which are trusted by definition. For this reason the issue was assessed
as Moderate severity.

The FIPS modules in 3.6, 3.5 and 3.4 are not affected by this issue, as
PKCS#12 processing is outside the OpenSSL FIPS module boundary.

OpenSSL 3.6, 3.5 and 3.4 are vulnerable to this issue.

OpenSSL 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue as they do
not support PBMAC1 in PKCS#12.

OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.

OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.

OpenSSL 3.4 users should upgrade to OpenSSL 3.4.4.

This issue was reported on 11th September 2025 by Stanislav Fort
(Aisle Research) with a follow up report on 21st November 2025 by
Stanislav Fort and Petr Šimeček (Aisle Research).
It was also independently reported on 14th October 2025 by Hamza
(Metadust).
The fix was developed by Tomas Mraz.

Stack buffer overflow in CMS AuthEnvelopedData parsing (CVE-2025-15467)
=======================================================================

Severity: High

Issue summary: Parsing CMS AuthEnvelopedData message with maliciously
crafted AEAD parameters can trigger a stack buffer overflow.

Impact summary: A stack buffer overflow may lead to a crash, causing Denial
of Service, or potentially remote code execution.

When parsing CMS AuthEnvelopedData structures that use AEAD ciphers such as
AES-GCM, the IV (Initialization Vector) encoded in the ASN.1 parameters is
copied into a fixed-size stack buffer without verifying that its length fits
the destination. An attacker can supply a crafted CMS message with an
oversized IV, causing a stack-based out-of-bounds write before any
authentication or tag verification occurs.

Applications and services that parse untrusted CMS or PKCS#7 content using
AEAD ciphers (e.g., S/MIME AuthEnvelopedData with AES-GCM) are vulnerable.
Because the overflow occurs prior to authentication, no valid key material
is required to trigger it. While exploitability to remote code execution
depends on platform and toolchain mitigations, the stack-based write
primitive represents a severe risk.

The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this
issue, as the CMS implementation is outside the OpenSSL FIPS module
boundary.

OpenSSL 3.6, 3.5, 3.4, 3.3 and 3.0 are vulnerable to this issue.

OpenSSL 1.1.1 and 1.0.2 are not affected by this issue.

OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.

OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.

OpenSSL 3.4 users should upgrade to OpenSSL 3.4.4.

OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6.

OpenSSL 3.0 users should upgrade to OpenSSL 3.0.19.

This issue was reported on 14th December 2025 by Stanislav Fort (Aisle
Research). The fix was developed by Igor Ustinov.

NULL dereference in SSL_CIPHER_find() function on unknown cipher ID (CVE-2025-15468)
====================================================================================

Severity: Low

Issue summary: If an application using the SSL_CIPHER_find() function in
a QUIC protocol client or server receives an unknown cipher suite from
the peer, a NULL dereference occurs.

Impact summary: A NULL pointer dereference leads to abnormal termination of
the running process causing Denial of Service.

Some applications call SSL_CIPHER_find() from the client_hello_cb callback
on the cipher ID received from the peer. If this is done with an SSL object
implementing the QUIC protocol, NULL pointer dereference will happen if
the examined cipher ID is unknown or unsupported.

As it is not very common to call this function in applications using the QUIC
protocol and the worst outcome is Denial of Service, the issue was assessed
as Low severity.

The vulnerable code was introduced in the 3.2 version with the addition
of the QUIC protocol support.

The FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue,
as the QUIC implementation is outside the OpenSSL FIPS module boundary.

OpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue.

OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue.

OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.

OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.

OpenSSL 3.4 users should upgrade to OpenSSL 3.4.4.

OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6.

This issue was reported on 13th December 2025 by Stanislav Fort (Aisle Research).
The fix was developed by Stanislav Fort (Aisle Research).

"openssl dgst" one-shot codepath silently truncates inputs >16MB (CVE-2025-15469)
=================================================================================

Severity: Low

Issue summary: The "openssl dgst" command-line tool silently truncates input
data to 16MB when using one-shot signing algorithms and reports success instead
of an error.

Impact summary: A user signing or verifying files larger than 16MB with
one-shot algorithms (such as Ed25519, Ed448, or ML-DSA) may believe the entire
file is authenticated while trailing data beyond 16MB remains unauthenticated.

When the "openssl dgst" command is used with algorithms that only support
one-shot signing (Ed25519, Ed448, ML-DSA-44, ML-DSA-65, ML-DSA-87), the input
is buffered with a 16MB limit. If the input exceeds this limit, the tool
silently truncates to the first 16MB and continues without signaling an error,
contrary to what the documentation states. This creates an integrity gap where
trailing bytes can be modified without detection if both signing and
verification are performed using the same affected codepath.

The issue affects only the command-line tool behavior. Verifiers that process
the full message using library APIs will reject the signature, so the risk
primarily affects workflows that both sign and verify with the affected
"openssl dgst" command. Streaming digest algorithms for "openssl dgst" and
library users are unaffected.

The FIPS modules in 3.5 and 3.6 are not affected by this issue, as the
command-line tools are outside the OpenSSL FIPS module boundary.

OpenSSL 3.5 and 3.6 are vulnerable to this issue.

OpenSSL 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue.

OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.

OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.

This issue was reported on 13th December 2025 by Stanislav Fort (Aisle
Research). The fix was developed by Viktor Dukhovni.

TLS 1.3 CompressedCertificate excessive memory allocation (CVE-2025-66199)
==========================================================================

Severity: Low

Issue summary: A TLS 1.3 connection using certificate compression can be
forced to allocate a large buffer before decompression without checking
against the configured certificate size limit.

Impact summary: An attacker can cause per-connection memory allocations of
up to approximately 22 MiB and extra CPU work, potentially leading to
service degradation or resource exhaustion (Denial of Service).

In affected configurations, the peer-supplied uncompressed certificate
length from a CompressedCertificate message is used to grow a heap buffer
prior to decompression. This length is not bounded by the max_cert_list
setting, which otherwise constrains certificate message sizes. An attacker
can exploit this to cause large per-connection allocations followed by
handshake failure. No memory corruption or information disclosure occurs.

This issue only affects builds where TLS 1.3 certificate compression is
compiled in (i.e., not OPENSSL_NO_COMP_ALG) and at least one compression
algorithm (brotli, zlib, or zstd) is available, and where the compression
extension is negotiated. Both clients receiving a server CompressedCertificate
and servers in mutual TLS scenarios receiving a client CompressedCertificate
are affected. Servers that do not request client certificates are not
vulnerable to client-initiated attacks.

Users can mitigate this issue by setting SSL_OP_NO_RX_CERTIFICATE_COMPRESSION
to disable receiving compressed certificates.

The FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue,
as the TLS implementation is outside the OpenSSL FIPS module boundary.

OpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue.

OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue.

OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.

OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.

OpenSSL 3.4 users should upgrade to OpenSSL 3.4.4.

OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6.

This issue was reported on 8th November 2025 by Tomas Dulka (Aisle Research)
and Stanislav Fort (Aisle Research). The fix was developed by Tomas Dulka
(Aisle Research) and Stanislav Fort (Aisle Research).

Heap out-of-bounds write in BIO_f_linebuffer on short writes (CVE-2025-68160)
==============================================================================

Severity: Low

Issue summary: Writing large, newline-free data into a BIO chain using the
line-buffering filter where the next BIO performs short writes can trigger
a heap-based out-of-bounds write.

Impact summary: This out-of-bounds write can cause memory corruption which
typically results in a crash, leading to Denial of Service for an application.

The line-buffering BIO filter (BIO_f_linebuffer) is not used by default in
TLS/SSL data paths. In OpenSSL command-line applications, it is typically
only pushed onto stdout/stderr on VMS systems. Third-party applications that
explicitly use this filter with a BIO chain that can short-write and that
write large, newline-free data influenced by an attacker would be affected.
However, the circumstances where this could happen are unlikely to be under
attacker control, and BIO_f_linebuffer is unlikely to be handling non-curated
data controlled by an attacker. For that reason the issue was assessed as
Low severity.

The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,
as the BIO implementation is outside the OpenSSL FIPS module boundary.

OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.

OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.

OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.

OpenSSL 3.4 users should upgrade to OpenSSL 3.4.4.

OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6.

OpenSSL 3.0 users should upgrade to OpenSSL 3.0.19.

OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1ze
(premium support customers only).

OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zn
(premium support customers only).

This issue was reported on 1st December 2025 by Petr Simecek (Aisle Research)
and Stanislav Fort (Aisle Research). The fix was developed by Stanislav Fort
(Aisle Research) and Neil Horman.

Unauthenticated/unencrypted trailing bytes with low-level OCB function calls (CVE-2025-69418)
=============================================================================================

Severity: Low

Issue summary: When using the low-level OCB API directly with AES-NI or
other hardware-accelerated code paths, inputs whose length is not a multiple
of 16 bytes can leave the final partial block unencrypted and unauthenticated.

Impact summary: The trailing 1-15 bytes of a message may be exposed in
cleartext on encryption and are not covered by the authentication tag,
allowing an attacker to read or tamper with those bytes without detection.

The low-level OCB encrypt and decrypt routines in the hardware-accelerated
stream path process full 16-byte blocks but do not advance the input/output
pointers. The subsequent tail-handling code then operates on the original
base pointers, effectively reprocessing the beginning of the buffer while
leaving the actual trailing bytes unprocessed. The authentication checksum
also excludes the true tail bytes.

However, typical OpenSSL consumers using EVP are not affected because the
higher-level EVP and provider OCB implementations split inputs so that full
blocks and trailing partial blocks are processed in separate calls, avoiding
the problematic code path. Additionally, TLS does not use OCB ciphersuites.
The vulnerability only affects applications that call the low-level
CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with
non-block-aligned lengths in a single call on hardware-accelerated builds.
For these reasons the issue was assessed as Low severity.

The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected
by this issue, as OCB mode is not a FIPS-approved algorithm.

OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.

OpenSSL 1.0.2 is not affected by this issue.

OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.

OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.

OpenSSL 3.4 users should upgrade to OpenSSL 3.4.4.

OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6.

OpenSSL 3.0 users should upgrade to OpenSSL 3.0.19.

OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1ze.
(premium support customers only).

This issue was reported on 16th December 2025 by Stanislav Fort (Aisle Research).
The fix was developed by Stanislav Fort (Aisle Research).

Out of bounds write in PKCS12_get_friendlyname() UTF-8 conversion (CVE-2025-69419)
==================================================================================

Severity: Low

Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously
crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing
non-ASCII BMP code point can trigger a one byte write before the allocated
buffer.

Impact summary: The out-of-bounds write can cause a memory corruption
which can have various consequences including a Denial of Service.

The OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12
BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes,
the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16
source byte count as the destination buffer capacity to UTF8_putc(). For BMP
code points above U+07FF, UTF-8 requires three bytes, but the forwarded
capacity can be just two bytes. UTF8_putc() then returns -1, and this negative
value is added to the output length without validation, causing the
length to become negative. The subsequent trailing NUL byte is then written
at a negative offset, causing write outside of heap allocated buffer.

The vulnerability is reachable via the public PKCS12_get_friendlyname() API
when parsing attacker-controlled PKCS#12 files. While PKCS12_parse() uses a
different code path that avoids this issue, PKCS12_get_friendlyname() directly
invokes the vulnerable function. Exploitation requires an attacker to provide
a malicious PKCS#12 file to be parsed by the application and the attacker
can just trigger a one zero byte write before the allocated buffer.
For that reason the issue was assessed as Low severity according to our
Security Policy.

The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,
as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.

OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.

OpenSSL 1.0.2 is not affected by this issue.

OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.

OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.

OpenSSL 3.4 users should upgrade to OpenSSL 3.4.4.

OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6.

OpenSSL 3.0 users should upgrade to OpenSSL 3.0.19.

OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1ze
(premium support customers only).

This issue was reported on 16th December 2025 by Stanislav Fort (Aisle Research).
The fix was developed by Norbert Pocs.

Missing ASN1_TYPE validation in TS_RESP_verify_response() function (CVE-2025-69420)
===================================================================================

Severity: Low

Issue summary: A type confusion vulnerability exists in the TimeStamp Response
verification code where an ASN1_TYPE union member is accessed without first
validating the type, causing an invalid or NULL pointer dereference when
processing a malformed TimeStamp Response file.

Impact summary: An application calling TS_RESP_verify_response() with a
malformed TimeStamp Response can be caused to dereference an invalid or
NULL pointer when reading, resulting in a Denial of Service.

The functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2()
access the signing cert attribute value without validating its type.
When the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory
through the ASN1_TYPE union, causing a crash.

Exploiting this vulnerability requires an attacker to provide a malformed
TimeStamp Response to an application that verifies timestamp responses. The
TimeStamp protocol (RFC 3161) is not widely used and the impact of the
exploit is just a Denial of Service. For these reasons the issue was
assessed as Low severity.

The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,
as the TimeStamp Response implementation is outside the OpenSSL FIPS module
boundary.

OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.

OpenSSL 1.0.2 is not affected by this issue.

OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.

OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.

OpenSSL 3.4 users should upgrade to OpenSSL 3.4.4.

OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6.

OpenSSL 3.0 users should upgrade to OpenSSL 3.0.19.

OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1ze.
(premium support customers only).

This issue was reported on 16th December 2025 by Luigino Camastra (Aisle Research).
The fix was developed by Bob Beck.

NULL Pointer Dereference in PKCS12_item_decrypt_d2i_ex function (CVE-2025-69421)
================================================================================

Severity: Low

Issue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer
dereference in the PKCS12_item_decrypt_d2i_ex() function.

Impact summary: A NULL pointer dereference can trigger a crash which leads to
Denial of Service for an application processing PKCS#12 files.

The PKCS12_item_decrypt_d2i_ex() function does not check whether the oct
parameter is NULL before dereferencing it. When called from
PKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can
be NULL, causing a crash. The vulnerability is limited to Denial of Service
and cannot be escalated to achieve code execution or memory disclosure.

Exploiting this issue requires an attacker to provide a malformed PKCS#12 file
to an application that processes it. For that reason the issue was assessed as
Low severity according to our Security Policy.

The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,
as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.

OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.

OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.

OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.

OpenSSL 3.4 users should upgrade to OpenSSL 3.4.4.

OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6.

OpenSSL 3.0 users should upgrade to OpenSSL 3.0.19.

OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1ze
(premium support customers only).

OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zn
(premium support customers only).

This issue was reported on 21st December 2025 by Luigino Camastra (Aisle Research).
The fix was developed by Luigino Camastra (Aisle Research).

Missing ASN1_TYPE validation in PKCS#12 parsing (CVE-2026-22795)
================================================================

Severity: Low

Issue summary: An invalid or NULL pointer dereference can happen in
an application processing a malformed PKCS#12 file.

Impact summary: An application processing a malformed PKCS#12 file can be
caused to dereference an invalid or NULL pointer on memory read, resulting
in a Denial of Service.

A type confusion vulnerability exists in PKCS#12 parsing code where
an ASN1_TYPE union member is accessed without first validating the type,
causing an invalid pointer read.

The location is constrained to a 1-byte address space, meaning any
attempted pointer manipulation can only target addresses between 0x00 and 0xFF.
This range corresponds to the zero page, which is unmapped on most modern
operating systems and will reliably result in a crash, leading only to a
Denial of Service. Exploiting this issue also requires a user or application
to process a maliciously crafted PKCS#12 file. It is uncommon to accept
untrusted PKCS#12 files in applications as they are usually used to store
private keys which are trusted by definition. For these reasons, the issue
was assessed as Low severity.

The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,
as the PKCS12 implementation is outside the OpenSSL FIPS module boundary.

OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.

OpenSSL 1.0.2 is not affected by this issue.

OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.

OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.

OpenSSL 3.4 users should upgrade to OpenSSL 3.4.4.

OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6.

OpenSSL 3.0 users should upgrade to OpenSSL 3.0.19.

OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1ze.
(premium support customers only).

This issue was reported on 8th January 2026 by Luigino Camastra (Aisle Research).
The fix was developed by Bob Beck.

ASN1_TYPE Type Confusion in the PKCS7_digest_from_attributes() function (CVE-2026-22796)
========================================================================================

Severity: Low

Issue summary: A type confusion vulnerability exists in the signature
verification of signed PKCS#7 data where an ASN1_TYPE union member is
accessed without first validating the type, causing an invalid or NULL
pointer dereference when processing malformed PKCS#7 data.

Impact summary: An application performing signature verification of PKCS#7
data or calling directly the PKCS7_digest_from_attributes() function can be
caused to dereference an invalid or NULL pointer when reading, resulting in
a Denial of Service.

The function PKCS7_digest_from_attributes() accesses the message digest attribute
value without validating its type. When the type is not V_ASN1_OCTET_STRING,
this results in accessing invalid memory through the ASN1_TYPE union, causing
a crash.

Exploiting this vulnerability requires an attacker to provide a malformed
signed PKCS#7 to an application that verifies it. The impact of the
exploit is just a Denial of Service, the PKCS7 API is legacy and applications
should be using the CMS API instead. For these reasons the issue was
assessed as Low severity.

The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,
as the PKCS#7 parsing implementation is outside the OpenSSL FIPS module
boundary.

OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.

OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.

OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.

OpenSSL 3.4 users should upgrade to OpenSSL 3.4.4.

OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6.

OpenSSL 3.0 users should upgrade to OpenSSL 3.0.19.

OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1ze.
(premium support customers only).

OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zn.
(premium support customers only).

This issue was reported on 8th January 2026 by Luigino Camastra (Aisle Research).
The fix was developed by Bob Beck.

General Advisory Notes
======================

URL for this Security Advisory:
https://openssl-library.org/news/secadv/20260127.txt

Note: the online version of the advisory may be updated with additional details
over time.

Only currently supported releases have been analysed. OpenSSL 3.1 and 3.2 are
out of support and have not been analysed.

For details of OpenSSL severity classifications please see:
https://openssl-library.org/policies/general/security-policy/

[https://openssl-library.org/news/secadv/20260127.txt](https://openssl-library.org/news/secadv/20260127.txt)


# ZDI-25-1072 | Zero Day Initiative
December 10th, 2025

IceWarp14 X-File-Operation Command Injection Remote Code Execution Vulnerability
--------------------------------------------------------------------------------

### ZDI-25-1072
ZDI-CAN-27394

* CVE ID: CVSS SCORE
  *                                                         CVE-2025-14500                                                    :                                                         9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
* CVE ID: AFFECTED VENDORS
  *                                                         CVE-2025-14500                                                    :                                                                                IceWarp
* CVE ID: AFFECTED PRODUCTS
  *                                                         CVE-2025-14500                                                    :                                                                                IceWarp
* CVE ID: VULNERABILITY DETAILS
  *                                                         CVE-2025-14500                                                    :                             This vulnerability allows remote attackers to execute arbitrary code on affected installations of IceWarp. Authentication is not required to exploit this vulnerability.The specific flaw exists within the handling of the X-File-Operation header. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of SYSTEM.
* CVE ID: ADDITIONAL DETAILS
  *                                                         CVE-2025-14500                                                    :                                                                                IceWarp has issued an update to correct this vulnerability. More details can be found at:                                                        https://support.icewarp.com/hc/en-us/community/posts/40040980098705-EPOS-Update-2-build-9-14-2-0-9
* CVE ID: DISCLOSURE TIMELINE
  *                                                         CVE-2025-14500                                                    :                                                             2025-09-26 - Vulnerability reported to vendor                                2025-12-10 - Coordinated public release of advisory                                2025-12-10 - Advisory Updated
* CVE ID: CREDIT
  *                                                         CVE-2025-14500                                                    : Oscar Bataille

[BACK TO ADVISORIES](https://www.zerodayinitiative.com/advisories/)


Cisco Catalyst SD-WAN Vulnerabilities

# Cisco Catalyst SD-WAN Vulnerabilities
*   These vulnerabilities are not dependent on one another. Exploitation of one of the vulnerabilities is not required to exploit another vulnerability.

    Details about the vulnerabilities are as follows:

    **CVE-2026-20129: Cisco Catalyst SD-WAN Manager Authentication Bypass Vulnerability**

    A vulnerability in the API user authentication of Cisco Catalyst SD-WAN Manager could allow an unauthenticated, remote attacker to gain access to an affected system as a user who has the _netadmin_ role.

    The vulnerability is due to improper authentication for requests that are sent to the API. An attacker could exploit this vulnerability by sending a crafted request to the API of an affected system. A successful exploit could allow the attacker to execute commands with the privileges of the _netadmin_ role.

    **Note:** Cisco Catalyst SD-WAN Manager releases 20.18 and later are not affected by this vulnerability.

    Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.

    Bug ID(s): [CSCws33587](https://bst.cisco.com/bugsearch/bug/CSCws33587)
    CVE ID: CVE-2026-20129
    Security Impact Rating (SIR): Critical
    CVSS Base Score: 9.8
    CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

    **CVE-2026-20126: Cisco Catalyst SD-WAN Manager Privilege Escalation Vulnerability**

    A vulnerability in Cisco Catalyst SD-WAN Manager could allow an authenticated, local attacker with low privileges to gain _root_ privileges on the underlying operating system.

    This vulnerability is due to an insufficient user authentication mechanism in the REST API. An attacker could exploit this vulnerability by sending a request to the REST API of the affected system. A successful exploit could allow the attacker to gain _root_ privileges on the underlying operating system.

    Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.

    Bug ID(s): [CSCws93470](https://bst.cisco.com/bugsearch/bug/CSCws93470)
    CVE ID: CVE-2026-20126
    Security Impact Rating (SIR): High
    CVSS Base Score: 7.8
    CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

    **CVE-2026-20133: Cisco Catalyst SD-WAN Manager Information Disclosure Vulnerability**

    A vulnerability in Cisco Catalyst SD-WAN Manager could allow an unauthenticated, remote attacker to view sensitive information on an affected system.

    This vulnerability is due to insufficient file system access restrictions. An attacker could exploit this vulnerability by accessing the API of an affected system. A successful exploit could allow the attacker to read sensitive information on the underlying operating system.

    Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.

    Bug ID(s): [CSCws33583](https://bst.cisco.com/bugsearch/bug/CSCws33583)
    CVE ID: CVE-2026-20133
    Security Impact Rating (SIR): High
    CVSS Base Score: 7.5
    CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

    **CVE-2026-20122: Cisco Catalyst SD-WAN Manager Arbitrary File Overwrite Vulnerability**

    A vulnerability in the API of Cisco Catalyst SD-WAN Manager could allow an authenticated, remote attacker to overwrite arbitrary files on the local file system. To exploit this vulnerability, the attacker must have valid _read-only_ credentials with API access on the affected system.

    This vulnerability is due to improper file handling on the API interface of an affected system. An attacker could exploit this vulnerability by uploading a malicious file on the local file system. A successful exploit could allow the attacker to overwrite arbitrary files on the affected system and gain _vmanage_ user privileges.

    Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.

    Bug ID(s): [CSCws33584](https://bst.cisco.com/bugsearch/bug/CSCws33584), [CSCws33586](https://bst.cisco.com/bugsearch/bug/CSCws33586)
    CVE ID: CVE-2026-20122
    Security Impact Rating (SIR): High
    CVSS Base Score: 7.1
    CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L

    **CVE-2026-20128: Cisco Catalyst SD-WAN Manager Information Disclosure Vulnerability**

    A vulnerability in the Data Collection Agent (DCA) feature of Cisco Catalyst SD-WAN Manager could allow an authenticated, local attacker to gain DCA user privileges on an affected system. To exploit this vulnerability, the attacker must have valid _vmanage_ credentials on the affected system.

    This vulnerability is due to the presence of a credential file for the DCA user on an affected system. An attacker could exploit this vulnerability by accessing the filesystem as a low-privileged user and reading the file that contains the DCA password from that affected system. A successful exploit could allow the attacker to access another affected system and gain DCA user privileges.

    **Note:** Cisco Catalyst SD-WAN Manager releases 20.18 and later are not affected by this vulnerability.

    Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.

    Bug ID(s): [CSCws33585](https://bst.cisco.com/bugsearch/bug/CSCws33585)
    CVE ID: CVE-2026-20128
    Security Impact Rating (SIR): Medium
    CVSS Base Score: 5.5
    CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N


Lantronix EDS3000PS and EDS5000

# Lantronix EDS3000PS and EDS5000 | CISA
[**View CSAF**](https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-069-02.json)

Summary
-------

**Successful exploitation of these vulnerabilities could allow an attacker to bypass authentication and execute code with root-level privileges.**

The following versions of Lantronix EDS3000PS and EDS5000 are affected:

*   EDS3000PS 3.1.0.0R2 (CVE-2025-67039, CVE-2025-70082, CVE-2025-67041)
*   EDS5000 2.1.0.0R3 (CVE-2025-67034, CVE-2025-67035, CVE-2025-67036, CVE-2025-67037, CVE-2025-67038)

* CVSS: v3 9.8
  * Vendor: Lantronix
  * Equipment: Lantronix EDS3000PS and EDS5000
  * Vulnerabilities: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection'), Authentication Bypass Using an Alternate Path or Channel, Unverified Password Change

### Background

*   **Critical Infrastructure Sectors:** Communications, Information Technology, Critical Manufacturing
*   **Countries/Areas Deployed:** Worldwide
*   **Company Headquarters Location:** United States

* * *

Vulnerabilities
---------------

[Expand All +](#)

### [CVE-2025-67035](#)

An issue was discovered in Lantronix EDS5000 2.1.0.0R3. The SSH Client and SSH Server pages are affected by multiple OS injection vulnerabilities due to missing sanitization of input parameters. An attacker can inject arbitrary commands in delete actions of various objects, such as server keys, users, and known hosts. Commands are executed with root privileges.

[View CVE Details](https://nvd.nist.gov/vuln/detail/CVE-2025-67035)

* * *

#### Affected Products

##### Lantronix EDS3000PS and EDS5000

**Vendor:**
Lantronix

**Product Version:**
Lantronix EDS5000: 2.1.0.0R3

**Product Status:**
known\_affected

**Relevant CWE:** [CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')](https://cwe.mitre.org/data/definitions/78.html)

* * *

#### Metrics

### [CVE-2025-67038](#)

An issue was discovered in Lantronix EDS5000 2.1.0.0R3. The HTTP RPC module executes a shell command to write logs when user's authentication fails. The username is directly concatenated with the command without any sanitization. This allow attackers to inject arbitrary OS commands into the username parameter. Injected commands are executed with root privileges.

[View CVE Details](https://nvd.nist.gov/vuln/detail/CVE-2025-67038)

* * *

#### Affected Products

##### Lantronix EDS3000PS and EDS5000

**Vendor:**
Lantronix

**Product Version:**
Lantronix EDS5000: 2.1.0.0R3

**Product Status:**
known\_affected

**Relevant CWE:** [CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')](https://cwe.mitre.org/data/definitions/78.html)

* * *

#### Metrics

### [CVE-2025-67039](#)

An issue was discovered in Lantronix EDS3000PS 3.1.0.0R2. The authentication on management pages can be bypassed by appending a specific suffix to the URL and by sending an Authorization header that uses "admin" as the username.

[View CVE Details](https://nvd.nist.gov/vuln/detail/CVE-2025-67039)

* * *

#### Affected Products

##### Lantronix EDS3000PS and EDS5000

**Vendor:**
Lantronix

**Product Version:**
Lantronix EDS3000PS: 3.1.0.0R2

**Product Status:**
known\_affected

**Relevant CWE:** [CWE-288 Authentication Bypass Using an Alternate Path or Channel](https://cwe.mitre.org/data/definitions/288.html)

* * *

#### Metrics

### [CVE-2025-70082](#)

The administrator password can be changed without knowledge of the current password. When chained with an authentication bypass vulnerability, this issue may allow unauthenticated attackers to modify the administrator password.

[View CVE Details](https://nvd.nist.gov/vuln/detail/CVE-2025-70082)

* * *

#### Affected Products

##### Lantronix EDS3000PS and EDS5000

**Vendor:**
Lantronix

**Product Version:**
Lantronix EDS3000PS: 3.1.0.0R2

**Product Status:**
known\_affected

**Relevant CWE:** [CWE-620 Unverified Password Change](https://cwe.mitre.org/data/definitions/620.html)

* * *

#### Metrics

* * *

Acknowledgments
---------------

*   Francesco La Spina and Stanislav Dashevskyi of Forescout Technologies reported these vulnerabilities to CISA

* * *

Legal Notice and Terms of Use
-----------------------------

This product is provided subject to this Notification (https://www.cisa.gov/notification) and this Privacy & Use policy (https://www.cisa.gov/privacy-policy).

* * *

Recommended Practices
---------------------

CISA recommends users take defensive measures to minimize the risk of exploitation of these vulnerabilities, such as:

Minimize network exposure for all control system devices and/or systems, ensuring they are not accessible from the Internet.

Locate control system networks and remote devices behind firewalls and isolating them from business networks.

When remote access is required, use more secure methods, such as Virtual Private Networks (VPNs), recognizing VPNs may have vulnerabilities and should be updated to the most current version available. Also recognize VPN is only as secure as the connected devices.

CISA reminds organizations to perform proper impact analysis and risk assessment prior to deploying defensive measures.

CISA also provides a section for control systems security recommended practices on the ICS webpage on cisa.gov/ics. Several CISA products detailing cyber defense best practices are available for reading and download, including Improving Industrial Control Systems Cybersecurity with Defense-in-Depth Strategies.

CISA encourages organizations to implement recommended cybersecurity strategies for proactive defense of ICS assets.

Additional mitigation guidance and recommended practices are publicly available on the ICS webpage at cisa.gov/ics in the technical information paper, ICS-TIP-12-146-01B--Targeted Cyber Intrusion Detection and Mitigation Strategies.

Organizations observing suspected malicious activity should follow established internal procedures and report findings to CISA for tracking and correlation against other incidents.

CISA also recommends users take the following measures to protect themselves from social engineering attacks:

Do not click web links or open attachments in unsolicited email messages.

Refer to Recognizing and Avoiding Email Scams for more information on avoiding email scams.

Refer to Avoiding Social Engineering and Phishing Attacks for more information on social engineering attacks.

No known public exploitation specifically targeting these vulnerabilities has been reported to CISA at this time.

* * *

Revision History
----------------

*   **Initial Release Date:** 2026-03-10

|Date      |Revision|Summary            |
|----------|--------|-------------------|
|2026-03-10|1       |Initial Publication|

* * *

Legal Notice and Terms of Use
-----------------------------


# KB4830: Vulnerabilities Resolved in Veeam Backup & Replication 12.3.2.4465
Veeam Software Security Commitment

Veeam® is committed to ensuring its products protect customers from potential risks. As part of that commitment, we operate a [Vulnerability Disclosure Program (VDP)](https://www.veeam.com/vulnerability-disclosure.html) for all Veeam products and perform extensive internal code audits. When a vulnerability is identified, our team promptly develops a patch to address and mitigate the risk. In line with our dedication to transparency, we publicly disclose the vulnerability and provide detailed mitigation information. This approach ensures that all potentially affected customers can quickly implement the necessary measures to safeguard their systems. It’s important to note that once a vulnerability and its associated patch are disclosed, attackers will likely attempt to reverse-engineer the patch to exploit unpatched deployments of Veeam software. This reality underscores the critical importance of ensuring that all customers use the latest versions of our software and install all updates and patches without delay.

Issue Details
-------------

All vulnerabilities disclosed in this article affect **Veeam Backup & Replication 12.3.2.4165** and all [earlier version 12 builds](https://www.veeam.com/kb2680).

#### **CVE-2026-21666**

A vulnerability allowing an authenticated domain user to perform remote code execution (RCE) on the Backup Server.

**Severity:** Critical
**CVSS v3.1 Score:** 9.9CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
**Source:** Reported by HackerOne.

#### **CVE-2026-21667**

A vulnerability allowing an authenticated domain user to perform remote code execution (RCE) on the Backup Server.

**Severity:** Critical
**CVSS v3.1 Score:** 9.9CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
**Source:** Discovered during internal testing.

#### **CVE-2026-21668**

A vulnerability allowing an authenticated domain user to bypass restrictions and manipulate arbitrary files on a Backup Repository.

**Severity:** High
**CVSS v3.1 Score:** 8.8CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
**Source:** Discovered during internal testing.

#### **CVE-2026-21672**

A vulnerability allowing local privilege escalation on Windows-based Veeam Backup & Replication servers.

**Severity:** High
**CVSS v3.1 Score:** 8.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
**Source:** Reported through HackerOne.

#### **CVE-2026-21708**

A vulnerability allowing a Backup Viewer to perform remote code execution (RCE) as the `postgres` user.

**Severity:** Critical
**CVSS v3.1 Score:** 9.9CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
**Source:** Discovered during internal testing.

#### **Other Resolved Security-related Issues**

*   Veeam Agent _for Linux_ — Updated the port range that the software will open in the machine's firewall to align with other Veeam products. Veeam Agent _for Linux_ will now open ports 2500-3300.

Solution
--------

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a [Veeam Support Case.](https://www.veeam.com/kb1771)

To submit feedback regarding this article, please click this link: [Send Article Feedback](about:blank?ad=in-text-link#kb_request_form)
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.


Critical RCE Vulnerability reported in Windchill

#  Zero-day allows code execution in WindChill and FlexPLM | heise online

1.  Zero-day allows code execution in WindChill and FlexPLM
    *   [Many versions affected](#nav_many_versions__0 "Many versions affected")
    *   [Workaround: Restrict access via Apache configuration](#nav_workaround__1 "Workaround: Restrict access via Apache configuration")
    *   [Apparently active attacks – admins should keep their eyes open](#nav_apparently__2 "Apparently active attacks – admins should keep their eyes open")

The software Windchill and FlexPLM contains a security vulnerability that allows code execution. The manufacturer urgently calls for security measures to be taken – a patch is not yet available at the moment.

Information about the vulnerability is scarce; neither a CVE identifier nor warnings from national CERTs (Computer Emergency Response Team) are available. However, the manufacturer and its partners appear to be concerned: they are assigning the highest score of 10.0 points on the CVSS scale and urging customers to react immediately.

Apparently, the error is hidden in the deserialization of the servlets `/servlet/WindchillGW/com.ptc.wvs.server.publish.Publish` and `/servlet/WindchillAuthGW/com.ptc.wvs.server.publish.Publish`. If these are accessible to an attacker, for example, because the Windchill server is reachable from the internet, they can inject and execute code.

### Many versions affected

According to [the manufacturer PTC's extremely brief security notice](https://www.ptc.com/en/support/article/CS466318?_gl=1*196gmri*_gcl_au*Njc4ODc0NTE4LjE3NzQxNzI5NTc.*_ga*MTY0OTgyOTM1NC4xNzc0MTcyOTU2*_ga_7NMP2MSYPM*czE3NzQxNzI5NTYkbzEkZzAkdDE3NzQxNzI5ODQkajMyJGwwJGgw&as=0) in the Knowledge Base, the following versions are affected:

*   Windchill PDMLink 11.0 M030
*   Windchill PDMLink 11.1 M020
*   Windchill PDMLink 11.2.1.0
*   Windchill PDMLink 12.0.2.0
*   Windchill PDMLink 13.0.2.0
*   Windchill PDMLink 13.1.0.0
*   Windchill PDMLink 13.1.1.0
*   Windchill PDMLink 13.1.2.0
*   Windchill PDMLink 13.1.3.0
*   Windchill PDMLink 12.1.2.0
*   FlexPLM 11.0 M030
*   FlexPLM 11.1 M020
*   FlexPLM 11.2.1.0
*   FlexPLM 12.0.0.0
*   FlexPLM 12.0.2.0
*   FlexPLM 12.0.3.0
*   FlexPLM 12.1.2.0
*   FlexPLM 12.1.3.0
*   FlexPLM 13.0.2.0
*   FlexPLM 13.0.3.0

### Workaround: Restrict access via Apache configuration

Until a patch is available, admins should use a workaround. As described by the Windchill service provider EAC in a communication to its customers, this requires a configuration change to the Apache web server. According to EAC, this should be done **immediately** to neutralize the risk of an exploit.

1.  Create a new configuration file `<APACHE_HOME>/conf/conf.d/90-app-Windchill-Auth.conf`. (If a file with the prefix 90- or higher already exists, the new file should receive the highest number to be loaded as the last file)
2.  Incorporate the following directives into it:
    `<LocationMatch "^.*servlet/(WindchillGW|WindchillAuthGW)/com\.ptc\.wvs\.server\.publish\.Publish(?:;[^/]*)?/.*$">``Require all denied``</LocationMatch>`
3.  Restart the web server using the known commands.

### Apparently active attacks – admins should keep their eyes open

Although the manufacturer claims to have no knowledge of successful attacks, service provider EAC mentions some "[Indicators of Compromise](https://support.eacpds.com/hc/en-us/article_attachments/47430019070996)" (IOC). This means that attacks against Windchill or FlexPLM servers must have already occurred. The IOCs indicate that after a successful exploit, attackers upload files with malicious code to the server, typically web shells. Instances operated by PTC itself are already protected.

Insecure deserialization is a known entry point for exploits and is popular with cybercriminals and state-sponsored attackers. Just a few days ago, the US cybersecurity agency added another [deserialization vulnerability in Microsoft SharePoint](https://www.heise.de/news/Warnung-vor-Angriffen-auf-Cisco-FMC-SharePoint-und-Zimbra-11217003.html?from-en=1) to its database of Known Exploited Vulnerabilities.

([cku](mailto:cku@heise.de "Dr. Christopher Kunz"))

Don't miss any news – follow us on [Facebook](https://www.facebook.com/heiseonlineEnglish), [LinkedIn](https://www.linkedin.com/company/104691972) or [Mastodon](https://social.heise.de/@heiseonlineenglish).

_This article was originally published in [German](https://www.heise.de/news/Zero-Day-erlaubt-Codeausfuehrung-in-WindChill-und-FlexPLM-11220521.html). It was translated with technical assistance and editorially reviewed before publication._


# NetScaler ADC and NetScaler Gateway Security Bulletin for CVE-2026-3055 and CVE-2026-4368

### NetScaler ADC and NetScaler Gateway Security Bulletin for CVE-2026-3055 and CVE-2026-4368

#### Article ID: CTX696300

#### Description

NetScaler ADC and NetScaler Gateway are affected by the vulnerabilities mentioned below:

* CVE-ID: CVE-2026-3055
  * Description: Insufficient input validation leading to memory overread
  * Pre-conditions: Citrix ADC or Citrix Gateway must be configured as a SAML IDP
  * CWE: CWE-125: Out-of-bounds Read
  * CVSS v4.0: CVSS v4.0 Base Score: 9.3(CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L)
* CVE-ID: CVE-2026-4368
  * Description: Race Condition leading to User Session Mixup
  * Pre-conditions: Appliance must be configured as:Gateway (SSL VPN, ICA Proxy, CVPN, RDP Proxy)           OR AAA virtual server
  * CWE: CWE-362: Race Condition
  * CVSS v4.0: CVSS v4.0 Base Score: 7.7(CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N)

What Customers Should Do
------------------------

CVE 2026-3055 was identified internally through our ongoing security reviews and broader efforts to strengthen the security of the product.

Cloud Software Group strongly urges affected customers of NetScaler ADC and NetScaler Gateway to install the relevant updated versions as soon as possible.

*   NetScaler ADC and NetScaler Gateway 14.1-66.59 and later releases
*   NetScaler ADC and NetScaler Gateway 13.1-62.23 and later releases of 13.1
*   NetScaler ADC 13.1-FIPS and 13.1-NDcPP 13.1.37.262 and later releases of 13.1-FIPS and 13.1-NDcPP

**Note**: Customers are recommended to upgrade their appliances to one of the supported versions that address the vulnerabilities.

**CVE-2026-3055 :**

Customers can determine if they have an appliance configured as a SAML IDP Profile by inspecting their NetScaler Configuration for the specified string:

*   add authentication samlIdPProfile .\*

**CVE-2026-4368**

Customers can determine if they have an appliance configured as one of the following by inspecting their NetScaler Configuration for the specified strings

*   An Auth Server (AAA Vserver):
    *   add authentication vserver .\*
*   A Gateway (VPN Vserver,  ICA Proxy, CVPN, RDP Proxy) :
    *   add vpn vserver .\*

#### Environment

The information on this page is being provided to you on an "AS IS" and "AS-AVAILABLE" basis. The issues described on this page may or may not impact your system(s). Cloud Software Group Holdings, Inc. and its subsidiaries (collectively, "Cloud SG") make no representations, warranties, or guarantees as to the information contained herein. ANY AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE ARE HEREBY DISCLAIMED. BY ACCESSING THIS PAGE, YOU ACKNOWLEDGE THAT CLOUD SG SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE OUT OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN. Cloud SG reserves the right to change or update the information on this page at any time. We accordingly recommend that you always view the latest version of this page. The information contained herein is being provided to you under the terms of your applicable customer agreement with Cloud SG, and may be used only for the purposes contemplated by such agreement. If you do not have such an agreement with Cloud SG, this information is provided under the cloud.com Terms of Use, and may be used only for the purposes contemplated by such Terms of Use.

#### Issue/Introduction

Severity - Critical

Description of Problem
----------------------

Vulnerabilities have been discovered in NetScaler ADC (formerly Citrix ADC) and NetScaler Gateway (formerly Citrix Gateway). Refer below for further details.

Affected Versions:
------------------

The following supported versions of NetScaler ADC and NetScaler Gateway are affected by the vulnerabilities:

**CVE-2026-3055:**

*   NetScaler ADC and NetScaler Gateway 14.1 BEFORE 14.1-66.59
*   NetScaler ADC and NetScaler Gateway 13.1 BEFORE 13.1-62.23
*   NetScaler ADC FIPS and NDcPP BEFORE 13.1-37.262

**CVE-2026-4368:**

*   NetScaler ADC and NetScaler Gateway  14.1-66.54

**Note**: This bulletin only applies to customer-managed NetScaler ADC and NetScaler Gateway. Cloud Software Group upgrades Citrix-managed cloud services and Citrix-managed Adaptive Authentication with the necessary software updates.

#### Additional Information

What Citrix is Doing
--------------------

Citrix is notifying customers and channel partners about this potential security issue through the publication of this security bulletin on the Citrix Knowledge Center at [https://support.citrix.com/support-home/topic-article-list?trendingCategory=20&trendingTopicName=Security%20Bulletin](https://support.citrix.com/support-home/topic-article-list?trendingCategory=20&trendingTopicName=Security%20Bulletin)

Obtaining Support on This Issue
-------------------------------

If you require technical assistance with this issue, please contact Citrix Technical Support. Contact details for Citrix Technical Support are available at [https://support.citrix.com/support-home/home](https://support.citrix.com/support-home/home)

Subscribe to Receive Alerts
---------------------------

Citrix strongly recommends that all customers subscribe to receive alerts when a Citrix security bulletin is created or modified at [https://support.citrix.com/wolken-support/view/aboutsupport/my-support-alerts](https://support.citrix.com/wolken-support/view/aboutsupport/my-support-alerts)

Reporting Security Vulnerabilities to Citrix
--------------------------------------------

Citrix welcomes input regarding the security of its products and considers any and all potential vulnerabilities seriously. For details on our vulnerability response process and guidance on how to report security-related issues to Citrix, please see the following webpage: [https://www.cloud.com/trust-center/support](https://www.cloud.com/trust-center/support)