GitLab CE/EE versions from 9.3 up to but not including 18.11.6, 19.0 up to 19.0.3, and 19.1 up to 19.1.1 contain a vulnerability where sensitive information could be written to application logs due to insufficient filtering in a CI/CD API endpoint. This issue has been remediated in the specified fixed versions. The vulnerability is rated medium severity and no known exploits are reported in the wild.
GitLab CE/EE versions from 17.11 up to but not including 18.11.6, 19.0 up to 19.0.3, and 19.1 up to 19.1.1 contain an authorization vulnerability. This flaw could allow an authenticated user with developer-role permissions to bypass package protection rules and overwrite protected Maven package metadata. The issue arises from incorrect authorization checks under certain conditions. The vulnerability has been remediated in versions 18.11.6, 19.0.3, and 19.1.1.
GitLab CE/EE versions from 13.6 up to but not including 18.11.6, 19.0 up to 19.0.3, and 19.1 up to 19.1.1 contain an authorization vulnerability. Under certain conditions, an authenticated user with Reporter-level group permissions could view package metadata from projects with the Package Registry disabled. This occurs due to incorrect authorization checks in the group packages feature. The issue has been remediated in versions 18.11.6, 19.0.3, and 19.1.1.
A vulnerability in GitLab Enterprise Edition versions 18.6 up to but not including 18.11.6, 19.0 up to but not including 19.0.3, and 19.1 up to but not including 19.1.1 could allow an authenticated user to read or modify another group's virtual registry cleanup policy settings without proper authorization. This issue has been remediated in the specified fixed versions.
A vulnerability in GitLab Enterprise Edition versions 18.6 up to but not including 18.11.6, 19.0 up to but not including 19.0.3, and 19.1 up to but not including 19.1.1 could allow an authenticated user with limited permissions to access project information due to missing authorization checks. This issue has been remediated in the specified fixed versions. The severity of this vulnerability is considered low.
A vulnerability in GitLab CE/EE versions 17.5 up to but not including 18.11.6, 19.0 up to but not including 19.0.3, and 19.1 up to but not including 19.1.1 could allow an unauthenticated user to view confidential issue references on public projects due to missing authorization checks. This issue has been remediated in the specified fixed versions. The severity is assessed as medium.
GitLab CE/EE versions from 14.8 up to but not including 18.11.6, 19.0 up to but not including 19.0.3, and 19.1 up to but not including 19.1.1 contain a vulnerability where an authenticated user could conceal content within a Snippet due to improper input validation. This issue has been remediated in the specified fixed versions. The vulnerability is classified as medium severity and no known exploits are reported in the wild.
GitLab CE/EE versions from 8.3 up to but not including 18.11.6, 19.0 up to 19.0.3, and 19.1 up to 19.1.1 contain a vulnerability where an authenticated maintainer user could make requests to internal network resources via mirror synchronization due to improper URL validation relying on reverse DNS resolution. This issue has been remediated in the specified fixed versions.
A vulnerability in GitLab Enterprise Edition versions 19.1.0 up to but not including 19.1.1 allowed users under certain conditions to access sensitive information previously committed to a project. This was due to insufficient output filtering in Duo Workflows, which caused sensitive data to be inserted into log files. The issue has been remediated in version 19.1.1.
GitLab Enterprise Edition versions from 13.11 up to but not including 18.11.6, 19.0 up to 19.0.3, and 19.1 up to 19.1.1 contain an incorrect authorization vulnerability in DAST site profile management. This flaw could allow a user with Developer role to exfiltrate DAST site profile secrets under certain conditions. The issue has been remediated in versions 18.11.6, 19.0.3, and 19.1.1.
A cross-site scripting (XSS) vulnerability was identified in GitLab CE/EE affecting versions from 18.10 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1. This flaw allowed an unauthenticated user to execute arbitrary JavaScript in another user's browser session due to improper path validation under certain conditions. GitLab has released patches to remediate this issue.
A cross-site scripting (XSS) vulnerability exists in GitLab Enterprise Edition versions from 16.4 up to but not including 18.11.6, 19.0 up to but not including 19.0.3, and 19.1 up to but not including 19.1.1. This flaw allows an authenticated user with developer-role permissions to execute arbitrary client-side code in another user's session due to improper sanitization of user input. GitLab has released patches to remediate this issue.
GitLab EE versions from 17.9 up to but not including 18.11.6, 19.0 up to 19.0.3, and 19.1 up to 19.1.1 contain an authorization vulnerability. Under certain conditions, authenticated users with custom role permissions could view, create, or delete protected environment configurations even when CI/CD visibility was disabled for the project. This issue has been remediated in the specified fixed versions.
HAProxy versions prior to certain fixed releases contain a null pointer dereference vulnerability in the hpack_dht_insert() function. This flaw occurs when the return value of hpack_dht_defrag() is not validated under memory exhaustion conditions, allowing an attacker to cause a denial of service by crashing worker processes through HPACK dynamic table insertions under memory pressure.
A vulnerability has been found in MLflow up to 4666cffc7912ea606d592fc38d6a75e2935f65e7. The impacted element is an unknown function of the component Experiment-scoped Label Schema CRUD API. Such manipulation leads to missing authorization. It is possible to launch the attack remotely. A high complexity level is associated with this attack. The exploitability is regarded as difficult. The exploit has been disclosed to the public and may be used. A reply to the GitHub issue explains, that "[t]he labeling schema PR has not been merged yet. The auth handlers will be added before the release."
A vulnerability in the Node.js HTTP/2 client allows a malicious server to send an unlimited number of ORIGIN frames, which can cause an Out of Memory (OOM) error on the client. This affects multiple supported Node.js release lines including versions in the 22, 24, and 26 series, as well as specific Ubuntu package versions. The flaw can disrupt client operations by exhausting memory resources. A patch is available for the affected versions.
An inconsistency in hostname matching in Node.js can cause a trust-policy bypass in multi-context mutual TLS (mTLS) setups. This vulnerability affects specific versions in the Node.js 22, 24, and 26 release lines, as well as certain Ubuntu package versions. A patch is available to address this issue.
A critical vulnerability in Node.js TLS hostname handling allows embedded null characters in hostnames to cause silent authority rebinding due to C-string truncation in resolver bindings. This flaw affects multiple supported Node.js release lines including versions 22, 24, and 26, as well as specific Ubuntu package versions. The vulnerability can lead to incorrect hostname verification during TLS connections, potentially compromising confidentiality, integrity, and availability. A patch is available for the affected versions.
A vulnerability in the Node.js WebCrypto implementation causes the Node.js process to crash when the input to the subtle.encrypt() function is a multiple of 2 GiB. This affects multiple supported Node.js release lines including 22, 24, and 26, as well as specific Ubuntu package versions. Red Hat has issued security advisories with patches addressing this issue.