GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 that under certain conditions could have allowed an authenticated user to execute arbitrary code on the GitLab server due to an integer overflow issue when compiling a specially crafted regular expression in a CI/CD configuration.

redhat RHSA-2026:95655: RHSA-2026:95655: Satellite 6.16 EUS security update (Critical)

redhat RHSA-2026:95657: RHSA-2026:95657: Satellite 6.18 security update (Critical)

redhat RHSA-2026:95652: RHSA-2026:95652: Satellite 6.19 security update (Critical)

redhat RHSA-2026:95656: RHSA-2026:95656: Satellite 6.17 security update (Critical)

The version of Tencent Linux installed on the remote TencentOS Server 4 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2026:1331 advisory.

    Package updates are available for TencentOS Server 4 that fix the following vulnerabilities:

    CVE-2026-97229:
    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.8, 19.3 before     19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an unauthenticated user     to execute arbitrary code on the GitLab server via a specially crafted regular expression in a CI/CD     configuration, due to insufficient regular expression validation.

    CVE-2026-93577:
    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.7, 19.3 before     19.3.3, and 19.4 before 19.4.1 that under certain conditions could have allowed an authenticated user to     execute arbitrary code on the GitLab server due to an integer overflow issue when compiling a specially     crafted regular expression in a CI/CD configuration.

    CVE-2026-110264:
    An issue has been discovered in GitLab CE/EE affecting all versions from 7.0 before 18.11.13, 19.0 before     19.0.10, 19.1 before 19.1.9, 19.2 before 19.2.9, 19.3 before 19.3.6, 19.4 before 19.4.3, and 19.5 before     19.5.1 that, under certain conditions, could have allowed an unauthenticated user to execute arbitrary     code on the GitLab server due to integer overflow when compiling a specially crafted regular expression.

Tenable has extracted the preceding description block directly from the Tencent Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

There are packages installed that are affected by multiple vulnerabilities referenced in the following CVEs:

  - zlib is a Ruby interface for the zlib compression/decompression library. Versions 3.0.0 and below, 3.1.0,
    3.1.1, 3.2.0 and 3.2.1 contain a buffer overflow vulnerability in the Zlib::GzipReader. The
    zstream_buffer_ungets function prepends caller-provided bytes ahead of previously produced output but
    fails to guarantee the backing Ruby string has enough capacity before the memmove shifts the existing
    data. This can lead to memory corruption when the buffer length exceeds capacity. This issue has been
    fixed in versions 3.0.1, 3.1.2 and 3.2.3. (CVE-2026-27820)

  - ERB is a templating system for Ruby. Ruby 2.7.0 (before ERB 2.2.0 was published on rubygems.org)
    introduced an `@_init` instance variable guard in `ERB#result` and `ERB#run` to prevent code execution
    when an ERB object is reconstructed via `Marshal.load` (deserialization). However, three other public
    methods that also evaluate `@src` via `eval()` were not given the same guard: `ERB#def_method`,
    `ERB#def_module`, and `ERB#def_class`. An attacker who can trigger `Marshal.load` on untrusted data in a
    Ruby application that has `erb` loaded can use `ERB#def_module` (zero-arg, default parameters) as a code
    execution sink, bypassing the `@_init` protection entirely. ERB 4.0.3.1, 4.0.4.1, 6.0.1.1, and 6.0.4 patch
    the issue. (CVE-2026-41316)

  - An issue was discovered in the resolv gem before 0.7.2 for Ruby. Resolv::DNS::Resource.get_class,
    Resolv::DNS::Resource::Generic.create, and Resolv::DNS::SvcParam::Generic.create generate a new class for
    each unknown DNS resource record (type, class) pair, or each unknown SvcParamKey, encountered while
    decoding a response. Each generated class was permanently registered both as a constant on Resource (or
    SvcParam::Generic) and as an entry in a class-lookup hash (ClassHash), and thus the class remained
    reachable through that constant after the response was discarded. Type and class are each 16-bit values,
    and thus an attacker controlling DNS responses (a spoofed response, or a malicious or hijacked upstream
    DNS server) has roughly 2^32 distinct (type, class) pairs to choose from. A single response of a few
    hundred kilobytes carrying tens of thousands of distinct unknown types permanently grows process memory by
    tens of megabytes; repeated responses accumulate without bound and are never reclaimed by garbage
    collection, because the constant keeps each class alive. Any code path that calls
    Resolv::DNS::Message.decode on attacker-influenced DNS responses is affected. resolv is a default gem, and
    thus this is reachable from a plain Ruby installation without any additional dependency. (CVE-2026-80212)

  - An issue was discovered in the resolv gem before 0.7.2 for Ruby. Resolv::DNS::MessageEncoder wrote a DNS
    label's length into a single octet without checking its range. A label longer than 255 octets had its
    length stored modulo 256 but the label data was written unchanged, and thus the bytes on the wire
    described a different name than the one the application asked to encode. RFC 1035 section 2.3.4 limits a
    label to 63 octets, and the two high bits of the length octet are reserved for compression pointers.
    put_string packed the length with put_pack("C", d.length) and put_label used it for labels, and thus any
    value from 0 to 255 could end up as a label length octet, including the reserved 0x40-0xBF range and the
    0xC0-0xFF pointer range. Resolv::DNS::Name.create did not check per-label or total name length either, and
    thus an attacker-controlled hostname reached the encoder unchanged. An application that resolves an
    attacker-controlled hostname sends a query whose wire bytes name a domain the attacker chose. A hostname
    suffix that the application validates against an allowlist becomes padding that never appears on the wire,
    and thus allowlist and egress checks can be bypassed. The recursive resolver caches the response under the
    attacker's name, and DNS logs record that name rather than the one the application asked for. A label
    length whose low octet lands in the 0xC0-0xFF range produces a length octet that conforming parsers read
    as the start of a compression pointer, with the following attacker-controlled byte as the offset.
    (CVE-2026-80213)

There are packages installed that are affected by multiple vulnerabilities referenced in the following CVEs:

  - GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.8, 19.3 before
    19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an unauthenticated user
    to execute arbitrary code on the GitLab server via a specially crafted regular expression in a CI/CD
    configuration, due to insufficient regular expression validation. (CVE-2026-97229)

  - An issue was discovered in the resolv gem before 0.7.2 for Ruby. Resolv::DNS::Resource.get_class,
    Resolv::DNS::Resource::Generic.create, and Resolv::DNS::SvcParam::Generic.create generate a new class for
    each unknown DNS resource record (type, class) pair, or each unknown SvcParamKey, encountered while
    decoding a response. Each generated class was permanently registered both as a constant on Resource (or
    SvcParam::Generic) and as an entry in a class-lookup hash (ClassHash), and thus the class remained
    reachable through that constant after the response was discarded. Type and class are each 16-bit values,
    and thus an attacker controlling DNS responses (a spoofed response, or a malicious or hijacked upstream
    DNS server) has roughly 2^32 distinct (type, class) pairs to choose from. A single response of a few
    hundred kilobytes carrying tens of thousands of distinct unknown types permanently grows process memory by
    tens of megabytes; repeated responses accumulate without bound and are never reclaimed by garbage
    collection, because the constant keeps each class alive. Any code path that calls
    Resolv::DNS::Message.decode on attacker-influenced DNS responses is affected. resolv is a default gem, and
    thus this is reachable from a plain Ruby installation without any additional dependency. (CVE-2026-80212)

  - An issue was discovered in the resolv gem before 0.7.2 for Ruby. Resolv::DNS::MessageEncoder wrote a DNS
    label's length into a single octet without checking its range. A label longer than 255 octets had its
    length stored modulo 256 but the label data was written unchanged, and thus the bytes on the wire
    described a different name than the one the application asked to encode. RFC 1035 section 2.3.4 limits a
    label to 63 octets, and the two high bits of the length octet are reserved for compression pointers.
    put_string packed the length with put_pack("C", d.length) and put_label used it for labels, and thus any
    value from 0 to 255 could end up as a label length octet, including the reserved 0x40-0xBF range and the
    0xC0-0xFF pointer range. Resolv::DNS::Name.create did not check per-label or total name length either, and
    thus an attacker-controlled hostname reached the encoder unchanged. An application that resolves an
    attacker-controlled hostname sends a query whose wire bytes name a domain the attacker chose. A hostname
    suffix that the application validates against an allowlist becomes padding that never appears on the wire,
    and thus allowlist and egress checks can be bypassed. The recursive resolver caches the response under the
    attacker's name, and DNS logs record that name rather than the one the application asked for. A label
    length whose low octet lands in the 0xC0-0xFF range produces a length octet that conforming parsers read
    as the start of a compression pointer, with the following attacker-controlled byte as the offset.
    (CVE-2026-80213)

  - GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.7, 19.3 before
    19.3.3, and 19.4 before 19.4.1 that under certain conditions could have allowed an authenticated user to
    execute arbitrary code on the GitLab server due to a double free issue when parsing a specially crafted
    regular expression in a CI/CD configuration. (CVE-2026-89078)

  - GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.7, 19.3 before
    19.3.3, and 19.4 before 19.4.1 that under certain conditions could have allowed an authenticated user to
    execute arbitrary code on the GitLab server due to an integer overflow issue when compiling a specially
    crafted regular expression in a CI/CD configuration. (CVE-2026-93577)

The CentOS Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS7:CLSA-2026:1792791338 advisory.

  - An issue has been discovered in GitLab CE/EE affecting all versions from 7.0 before 18.11.13, 19.0 before     19.0.10, 19.1 before 19.1.9, 19.2 before 19.2.9, 19.3 before 19.3.6, 19.4 before 19.4.3, and 19.5 before     19.5.1 that, under certain conditions, could have allowed an unauthenticated user to execute arbitrary     code on the GitLab server due to integer overflow when compiling a specially crafted regular expression.
    (CVE-2026-110264)

  - GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.7, 19.3 before     19.3.3, and 19.4 before 19.4.1 that under certain conditions could have allowed an authenticated user to     execute arbitrary code on the GitLab server due to an integer overflow issue when compiling a specially     crafted regular expression in a CI/CD configuration. (CVE-2026-93577)

  - GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.8, 19.3 before     19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an unauthenticated user     to execute arbitrary code on the GitLab server via a specially crafted regular expression in a CI/CD     configuration, due to insufficient regular expression validation. (CVE-2026-97229)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.7, 19.3 before     19.3.3, and 19.4 before 19.4.1 that under certain conditions could have allowed an authenticated user to     execute arbitrary code on the GitLab server due to an integer overflow issue when compiling a specially     crafted regular expression in a CI/CD configuration. (CVE-2026-93577)

Note that Nessus relies on the presence of the package as reported by the vendor.

The AlmaLinux 9.2 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.2:CLSA-2026:1792800480 advisory.

  - An issue has been discovered in GitLab CE/EE affecting all versions from 7.0 before 18.11.13, 19.0 before     19.0.10, 19.1 before 19.1.9, 19.2 before 19.2.9, 19.3 before 19.3.6, 19.4 before 19.4.3, and 19.5 before     19.5.1 that, under certain conditions, could have allowed an unauthenticated user to execute arbitrary     code on the GitLab server due to integer overflow when compiling a specially crafted regular expression.
    (CVE-2026-110264)

  - GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.7, 19.3 before     19.3.3, and 19.4 before 19.4.1 that under certain conditions could have allowed an authenticated user to     execute arbitrary code on the GitLab server due to an integer overflow issue when compiling a specially     crafted regular expression in a CI/CD configuration. (CVE-2026-93577)

  - GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.8, 19.3 before     19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an unauthenticated user     to execute arbitrary code on the GitLab server via a specially crafted regular expression in a CI/CD     configuration, due to insufficient regular expression validation. (CVE-2026-97229)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The AlmaLinux 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.6:CLSA-2026:1792801476 advisory.

  - An issue has been discovered in GitLab CE/EE affecting all versions from 7.0 before 18.11.13, 19.0 before     19.0.10, 19.1 before 19.1.9, 19.2 before 19.2.9, 19.3 before 19.3.6, 19.4 before 19.4.3, and 19.5 before     19.5.1 that, under certain conditions, could have allowed an unauthenticated user to execute arbitrary     code on the GitLab server due to integer overflow when compiling a specially crafted regular expression.
    (CVE-2026-110264)

  - GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.7, 19.3 before     19.3.3, and 19.4 before 19.4.1 that under certain conditions could have allowed an authenticated user to     execute arbitrary code on the GitLab server due to an integer overflow issue when compiling a specially     crafted regular expression in a CI/CD configuration. (CVE-2026-93577)

  - GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.8, 19.3 before     19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an unauthenticated user     to execute arbitrary code on the GitLab server via a specially crafted regular expression in a CI/CD     configuration, due to insufficient regular expression validation. (CVE-2026-97229)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Rocky Linux 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.6:CLSA-2026:1792801476 advisory.

  - An issue has been discovered in GitLab CE/EE affecting all versions from 7.0 before 18.11.13, 19.0 before     19.0.10, 19.1 before 19.1.9, 19.2 before 19.2.9, 19.3 before 19.3.6, 19.4 before 19.4.3, and 19.5 before     19.5.1 that, under certain conditions, could have allowed an unauthenticated user to execute arbitrary     code on the GitLab server due to integer overflow when compiling a specially crafted regular expression.
    (CVE-2026-110264)

  - GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.7, 19.3 before     19.3.3, and 19.4 before 19.4.1 that under certain conditions could have allowed an authenticated user to     execute arbitrary code on the GitLab server due to an integer overflow issue when compiling a specially     crafted regular expression in a CI/CD configuration. (CVE-2026-93577)

  - GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.8, 19.3 before     19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an unauthenticated user     to execute arbitrary code on the GitLab server via a specially crafted regular expression in a CI/CD     configuration, due to insufficient regular expression validation. (CVE-2026-97229)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the 3f11e437-b7cd-11f1-a883-2cf05da270f3 advisory.

    Gitlab reports:
    Double Free issue in Regular Expression Parser impacts GitLab CE/EE     Integer Overflow issue in Regular Expression Compiler impacts GitLab CE/EE     Cross-site Scripting issue in merge request diff viewer impacts GitLab CE/EE     Missing Authorization issue in Duo AI job troubleshooting feature impacts GitLab EE     Incorrect Authorization issue in MCP API scope enforcement impacts GitLab CE/EE     Use of Less Trusted Source issue in Direct Transfer import user mapping impacts GitLab CE/EE     Missing Authorization issue in Epic Issues REST API impacts GitLab CE/EE     Incorrect Authorization issue in Duo Workflow Service token governance enforcement impacts GitLab EE     Improper Access Control issue in GraphQL memberRoles dependentSecurityPolicies resolver impacts GitLab EE     Missing Authorization issue in GraphQL CI job trace API impacts GitLab CE/EE     Race Condition issue in MCP gitlab_search tool impacts GitLab CE/EE

Tenable has extracted the preceding description block directly from the FreeBSD security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of GitLab installed on the remote host is affected by a vulnerability, as follows:

  - GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.7, 19.3 before     19.3.3, and 19.4 before 19.4.1 that under certain conditions could have allowed an authenticated user to     execute arbitrary code on the GitLab server due to an integer overflow issue when compiling a specially     crafted regular expression in a CI/CD configuration. (CVE-2026-93577)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Type	Severity
376204	TencentOS Server 4: ruby (TSSA-2026:1331)	Nessus	Tencent Local Security Checks	Local	critical
477565	Alpine: multiple ruby packages: security update to 3.3.13-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	Local	medium
477565	Alpine: multiple ruby packages: security update to 3.3.13-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	Local	medium
477499	Alpine: multiple ruby packages: security update to 3.4.12-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	Local	critical
477499	Alpine: multiple ruby packages: security update to 3.4.12-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	Local	critical
372091	CentOS Linux 7 [TuxCare] Security Update: ruby / ruby-devel / ruby-doc / ruby-irb / ruby-libs / ruby-tcltk / etc Multiple Vulnerabilities (CENTOS7:CLSA-2026:1792791338)	Nessus	CentOS Local Security Checks	Local	critical
371749	Linux Distros Unpatched Vulnerability : CVE-2026-93577	Nessus	Misc.	Local	critical
371615	AlmaLinux 9.2 [TuxCare] Security Update: ruby / ruby-default-gems / ruby-devel / ruby-doc / ruby-libs / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1792800480)	Nessus	Alma Linux Local Security Checks	Local	critical
371613	AlmaLinux 9.6 [TuxCare] Security Update: ruby / ruby-default-gems / ruby-devel / ruby-doc / ruby-libs / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1792801476)	Nessus	Alma Linux Local Security Checks	Local	critical
371609	Rocky Linux 9.6 [TuxCare] Security Update: ruby / ruby-default-gems / ruby-devel / ruby-doc / ruby-libs / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1792801476)	Nessus	Rocky Linux Local Security Checks	Local	critical
349792	FreeBSD : Gitlab -- vulnerabilities (3f11e437-b7cd-11f1-a883-2cf05da270f3)	Nessus	FreeBSD Local Security Checks	Local	critical
349554	GitLab 19.2 < 19.2.7 / 19.3 < 19.3.3 / 19.4 < 19.4.1 (CVE-2026-93577)	Nessus	CGI abuses	Combined	critical

Detections

Analytics

CVE-2026-93577

critical

Tenable Plugins

Coming Soon

critical

medium

medium

critical

critical

critical

critical

critical

critical

critical

critical

critical