CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

GitLab

product · product:gitlab single-sourcesingle-source-national-cert

Coverage
5
first 2026-08-19 → last 2026-10-14
Latest activity
2026-10-14
GitLab's CVSS 10.0 CI regex flaw now has a public PoC; the demonstrated path needs push access to a public…
Peak priority
high
3 high · 2 notable
Targets
technology
sectors: technology, public-sector, healthcare · regions: europe
Sources cited
25
17 hosts

Action items (4)

Do-now tasks recorded on the entries about GitLab, newest first. Check the date before acting on an older one.

  • Upgrade every self-managed GitLab CE and EE instance on 19.2, 19.3 or 19.4 to 19.2.8, 19.3.5 or 19.4.2 now, internet-reachable instances and instances that allow open sign-up or public projects first, because a public proof of concept exists; 19.4.1 and 19.3.4 remain affected, and until each instance is upgraded, restrict anonymous access to public projects and stop untrusted users from creating or writing to public projects, which reduces exposure only to the path Rapid7 demonstrated.
    2026-10-13CVE-2026-97229
  • Upgrade every self-managed GitLab CE/EE instance to 19.3.2 / 19.2.6 / 19.1.8 now, or on the 19.0 and 18.11 trains to the 19.0.9 / 18.11.12 backports, which carry only the CVE-2026-85706 and CVE-2026-87719 fixes and leave GitLab EE exposed to CVE-2026-88765 until 19.1.8 or later; GitLab.com is already patched and GitLab Dedicated needs no action. Assume any files an attacker-scripted request could reach (configuration files, secrets or other sensitive server-side data) may have been read, and rotate them if the instance was internet-reachable and unpatched since 2026-09-10.
    2026-09-12CVE-2026-85706 +2
  • Upgrade every self-managed GitLab instance to 18.11.11, 19.0.8, 19.1.6 or 19.2.4 for its line; GitLab states these releases carry no new migrations and should need no downtime on multi-node deployments, which removes the usual reason to defer.
    2026-08-19CVE-2026-19478 +1
  • Search web and reverse-proxy access logs for requests to the GraphQL API endpoint carrying the string @gl_introduced, and treat any unauthenticated request to that endpoint as a probe or an exploitation attempt. Because the flaw's impact is modification and deletion rather than disclosure, pair the log search with a check of project and user-data integrity against backups over the window from 2026-08-17 onward, on any self-managed instance that was internet-reachable and unpatched.
    2026-08-19CVE-2026-19478 +1

Defender insights

What each entry about GitLab tells a defender to do, newest first.

2026-10-13HIGHGitLab's CVSS 10.0 CI regex flaw now has a public PoC; the demonstrated path needs push access to a public project

Exposure · triage · detection

2026-09-12HIGHexploitedGitLab's maximum-severity file-read flaw drew in-the-wild probes by the day after its patch

Triage

2026-10-09NOTABLEexploitedJoint advisory: Flax Typhoon-consistent actors spray Exchange and Microsoft 365, steal mail and keep SoftEther access

Exposure · triage · detection

2026-10-07NOTABLECloudSEK: a Gentlemen affiliate reached victims through stolen GitLab CI/CD secrets and drove attacks over MCP

Exposure · triage · detection

2026-08-19HIGHexploitedGitLab breaks its own release cadence for a pre-auth flaw whose impact is destruction, not disclosure

Triage

Story timeline

  1. 2026-10-13CVE-2026-97229, GitLab CE/EE: an integer overflow in the CI/CD regular-expression compiler allows code execution on self-managed servers and now has a public proof of concept; fixed in 19.4.2, 19.3.5 and 19.2.8, and 19.4.1 does not close it (CVSS 10.0)
    trending-vulnerabilitiesGitLab's CVSS 10.0 CI regex flaw now has a public PoC; the demonstrated path needs push access to a public project
  2. 2026-10-09AA26-281A: China-linked actors enabled by Integrity Technology Group scan with MicroScan, spray Exchange and Microsoft 365 passwords and steal mail, and five old flaws from the scanner's scripts enter CISA KEV
    active-threatsJoint advisory: Flax Typhoon-consistent actors spray Exchange and Microsoft 365, steal mail and keep SoftEther access
  3. 2026-10-07A Gentlemen ransomware affiliate ran his own leak site and reached his victims through stolen CI/CD secrets, with attack commands driven through an MCP server (CloudSEK)
    active-threatsCloudSEK: a Gentlemen affiliate reached victims through stolen GitLab CI/CD secrets and drove attacks over MCP
  4. 2026-09-12CVE-2026-85706, GitLab CE/EE: unauthenticated path traversal in the repository commits API reads arbitrary server files, and honeypots recorded probes by the day after the patch (CVSS 10.0)
    trending-vulnerabilitiesGitLab's maximum-severity file-read flaw drew in-the-wild probes by the day after its patch
  5. 2026-08-19CVE-2026-19478; GitLab ships an out-of-band critical patch for a GraphQL directive flaw that lets an unauthenticated caller modify or delete public projects and user data (CVSS 9.4)
    trending-vulnerabilitiesGitLab breaks its own release cadence for a pre-auth flaw whose impact is destruction, not disclosure
ATT&CK techniques (25 across 10 tactics)

25 techniques observed across 5 entries about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.0 · compare on the matrix · Navigator layer (JSON)

  • ReconnaissanceActive Scanning: Vulnerability Scanning
  • Initial AccessValid Accounts · External Remote Services · Drive-by Compromise · Exploit Public-Facing Application
  • ExecutionCommand and Scripting Interpreter: PowerShell · Command and Scripting Interpreter: Unix Shell · Command and Scripting Interpreter: Python · Command and Scripting Interpreter: JavaScript
  • PersistenceValid Accounts · External Remote Services
  • Privilege EscalationValid Accounts
  • StealthMasquerading: Rename Legitimate Utilities · Valid Accounts
  • Credential AccessOS Credential Dumping: DCSync · Brute Force: Password Guessing · Brute Force: Password Cracking · Brute Force: Password Spraying · Unsecured Credentials: Credentials In Files · Unsecured Credentials: Private Keys
  • CollectionData Staged: Local Data Staging · Email Collection: Remote Email Collection · Data from Information Repositories: Code Repositories · Data from Cloud Storage · Archive Collected Data: Archive via Custom Method
  • ExfiltrationAutomated Exfiltration · Exfiltration Over Web Service: Exfiltration to Cloud Storage
  • ImpactData Destruction · Defacement: Internal Defacement

Reconnaissance TA0043

T1595.002Active Scanning: Vulnerability Scanning×1

Adversaries may scan victims for vulnerabilities that can be used during targeting. Vulnerability scans typically check if the configuration of a target host/application (ex: software and version) potentially aligns with the target of a specific exploit the adversary may seek to use.

Evidence: 2026-10-09/aa26-281a-integrity-tech-microscan-exchange-mail-theft · ATT&CK page ↗

Initial Access TA0001

T1078Valid Accounts×1

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-10-07/gentlemen-affiliate-azazel-ci-cd-secrets-mcp-attacks · ATT&CK page ↗

T1133External Remote Services×1

Adversaries may leverage external-facing remote services to initially access and/or persist within a network. Remote services such as VPNs, Citrix, and other access mechanisms allow users to connect to internal enterprise network resources from external locations. There are often remote service gateways that manage connections and credential authentication for these services. Services such as Windows Remote Management and VNC can also be used externally.

Evidence: 2026-10-09/aa26-281a-integrity-tech-microscan-exchange-mail-theft · ATT&CK page ↗

T1189Drive-by Compromise×1

Adversaries may gain access to a system through a user visiting a website over the normal course of browsing. Multiple ways of delivering exploit code to a browser exist (i.e., Drive-by Target), including:

Evidence: 2026-10-09/aa26-281a-integrity-tech-microscan-exchange-mail-theft · ATT&CK page ↗

T1190Exploit Public-Facing Application×5

Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.

Evidence: 2026-10-13/cve-2026-97229-gitlab-ci-regex-compiler-unauthenticated-rce · 2026-10-09/aa26-281a-integrity-tech-microscan-exchange-mail-theft · 2026-10-07/gentlemen-affiliate-azazel-ci-cd-secrets-mcp-attacks · 2026-09-12/cve-2026-85706-gitlab-unauth-path-traversal-file-read · 2026-08-19/cve-2026-19478-gitlab-graphql-unauth-data-destruction · ATT&CK page ↗

Execution TA0002

T1059.001Command and Scripting Interpreter: PowerShell×1

Adversaries may abuse PowerShell commands and scripts for execution. PowerShell is a powerful interactive command-line interface and scripting environment included in the Windows operating system. PowerShell can also be installed on Linux and macOS. Adversaries can use PowerShell to perform a number of actions, including discovery of information and execution of code. Examples include the <code>Start-Process</code> cmdlet which can be used to run an executable and the <code>Invoke-Command</code> cmdlet which runs a command locally or on a remote computer (though administrator permissions are required to use PowerShell to connect to remote systems).

Evidence: 2026-10-09/aa26-281a-integrity-tech-microscan-exchange-mail-theft · ATT&CK page ↗

T1059.004Command and Scripting Interpreter: Unix Shell×1

Adversaries may abuse Unix shell commands and scripts for execution. Unix shells are the primary command prompt on Linux, macOS, and ESXi systems, though many variations of the Unix shell exist (e.g. sh, ash, bash, zsh, etc.) depending on the specific OS or distribution. Unix shells can control every aspect of a system, with certain commands requiring elevated privileges.

Evidence: 2026-10-09/aa26-281a-integrity-tech-microscan-exchange-mail-theft · ATT&CK page ↗

T1059.006Command and Scripting Interpreter: Python×1

Adversaries may abuse Python commands and scripts for execution. Python is a very popular scripting/programming language, with capabilities to perform many functions. Python can be executed interactively from the command-line (via the <code>python.exe</code> interpreter) or via scripts (.py) that can be written and distributed to different systems. Python code can also be compiled into binary executables.

Evidence: 2026-10-09/aa26-281a-integrity-tech-microscan-exchange-mail-theft · ATT&CK page ↗

T1059.007Command and Scripting Interpreter: JavaScript×1

Adversaries may abuse various implementations of JavaScript for execution. JavaScript (JS) is a platform-independent scripting language (compiled just-in-time at runtime) commonly associated with scripts in webpages, though JS can be executed in runtime environments outside the browser.

Evidence: 2026-10-09/aa26-281a-integrity-tech-microscan-exchange-mail-theft · ATT&CK page ↗

Persistence TA0003

T1078Valid Accounts×1

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-10-07/gentlemen-affiliate-azazel-ci-cd-secrets-mcp-attacks · ATT&CK page ↗

T1133External Remote Services×1

Adversaries may leverage external-facing remote services to initially access and/or persist within a network. Remote services such as VPNs, Citrix, and other access mechanisms allow users to connect to internal enterprise network resources from external locations. There are often remote service gateways that manage connections and credential authentication for these services. Services such as Windows Remote Management and VNC can also be used externally.

Evidence: 2026-10-09/aa26-281a-integrity-tech-microscan-exchange-mail-theft · ATT&CK page ↗

Privilege Escalation TA0004

T1078Valid Accounts×1

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-10-07/gentlemen-affiliate-azazel-ci-cd-secrets-mcp-attacks · ATT&CK page ↗

Stealth TA0005

T1036.003Masquerading: Rename Legitimate Utilities×1

Adversaries may rename legitimate / system utilities to try to evade security mechanisms concerning the usage of those utilities. Security monitoring and control mechanisms may be in place for legitimate utilities adversaries are capable of abusing, including both built-in binaries and tools such as PSExec, AutoHotKey, and IronPython. It may be possible to bypass those security mechanisms by renaming the utility prior to utilization (ex: rename <code>rundll32.exe</code>). An alternative case occurs when a legitimate utility is copied or moved to a different directory and renamed to avoid detections based on these utilities executing from non-standard paths.

Evidence: 2026-10-09/aa26-281a-integrity-tech-microscan-exchange-mail-theft · ATT&CK page ↗

T1078Valid Accounts×1

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-10-07/gentlemen-affiliate-azazel-ci-cd-secrets-mcp-attacks · ATT&CK page ↗

Credential Access TA0006

T1003.006OS Credential Dumping: DCSync×1

Adversaries may attempt to access credentials and other sensitive information by abusing a Windows Domain Controller's application programming interface (API) to simulate the replication process from a remote domain controller using a technique called DCSync.

Evidence: 2026-10-09/aa26-281a-integrity-tech-microscan-exchange-mail-theft · ATT&CK page ↗

T1110.001Brute Force: Password Guessing×1

Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts. Without knowledge of the password for an account, an adversary may opt to systematically guess the password using a repetitive or iterative mechanism. An adversary may guess login credentials without prior knowledge of system or environment passwords during an operation by using a list of common passwords. Password guessing may or may not take into account the target's policies on password complexity or use policies that may lock accounts out after a number of failed attempts.

Evidence: 2026-10-09/aa26-281a-integrity-tech-microscan-exchange-mail-theft · ATT&CK page ↗

T1110.002Brute Force: Password Cracking×1

Adversaries may use password cracking to attempt to recover usable credentials, such as plaintext passwords, when credential material such as password hashes are obtained. OS Credential Dumping can be used to obtain password hashes, this may only get an adversary so far when Pass the Hash is not an option. Further, adversaries may leverage Data from Configuration Repository in order to obtain hashed credentials for network devices.

Evidence: 2026-10-07/gentlemen-affiliate-azazel-ci-cd-secrets-mcp-attacks · ATT&CK page ↗

T1110.003Brute Force: Password Spraying×1

Adversaries may use a single or small list of commonly used passwords against many different accounts to attempt to acquire valid account credentials. Password spraying uses one password (e.g. 'Password01'), or a small list of commonly used passwords, that may match the complexity policy of the domain. Logins are attempted with that password against many different accounts on a network to avoid account lockouts that would normally occur when brute forcing a single account with many passwords.

Evidence: 2026-10-09/aa26-281a-integrity-tech-microscan-exchange-mail-theft · ATT&CK page ↗

T1552.001Unsecured Credentials: Credentials In Files×2

Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials. These can be files created by users to store their own credentials, shared credential stores for a group of individuals, configuration files containing passwords for a system or service, or source code/binary files containing embedded passwords.

Evidence: 2026-10-07/gentlemen-affiliate-azazel-ci-cd-secrets-mcp-attacks · 2026-09-12/cve-2026-85706-gitlab-unauth-path-traversal-file-read · ATT&CK page ↗

T1552.004Unsecured Credentials: Private Keys×1

Adversaries may search for private key certificate files on compromised systems for insecurely stored credentials. Private cryptographic keys and certificates are used for authentication, encryption/decryption, and digital signatures. Common key and certificate file extensions include: .key, .pgp, .gpg, .ppk., .p12, .pem, .pfx, .cer, .p7b, .asc.

Evidence: 2026-10-07/gentlemen-affiliate-azazel-ci-cd-secrets-mcp-attacks · ATT&CK page ↗

Collection TA0009

T1074.001Data Staged: Local Data Staging×1

Adversaries may stage collected data in a central location or directory on the local system prior to Exfiltration. Data may be kept in separate files or combined into one file through techniques such as Archive Collected Data. Interactive command shells may be used, and common functionality within cmd and bash may be used to copy data into a staging location.

Evidence: 2026-10-09/aa26-281a-integrity-tech-microscan-exchange-mail-theft · ATT&CK page ↗

T1114.002Email Collection: Remote Email Collection×1

Adversaries may target an Exchange server, Office 365, or Google Workspace to collect sensitive information. Adversaries may leverage a user's credentials and interact directly with the Exchange server to acquire information from within a network. Adversaries may also access externally facing Exchange services, Office 365, or Google Workspace to access email using credentials or access tokens. Tools such as MailSniper can be used to automate searches for specific keywords.

Evidence: 2026-10-09/aa26-281a-integrity-tech-microscan-exchange-mail-theft · ATT&CK page ↗

T1213.003Data from Information Repositories: Code Repositories×1

Adversaries may leverage code repositories to collect valuable information. Code repositories are tools/services that store source code and automate software builds. They may be hosted internally or privately on third party sites such as Github, GitLab, SourceForge, and BitBucket. Users typically interact with code repositories through a web application or command-line utilities such as git.

Evidence: 2026-10-07/gentlemen-affiliate-azazel-ci-cd-secrets-mcp-attacks · ATT&CK page ↗

T1530Data from Cloud Storage×1

Adversaries may access data from cloud storage.

Evidence: 2026-10-07/gentlemen-affiliate-azazel-ci-cd-secrets-mcp-attacks · ATT&CK page ↗

T1560.003Archive Collected Data: Archive via Custom Method×1

An adversary may compress or encrypt data that is collected prior to exfiltration using a custom method. Adversaries may choose to use custom archival methods, such as encryption with XOR or stream ciphers implemented with no external library or utility references. Custom implementations of well-known compression algorithms have also been used.

Evidence: 2026-10-09/aa26-281a-integrity-tech-microscan-exchange-mail-theft · ATT&CK page ↗

Exfiltration TA0010

T1020Automated Exfiltration×1

Adversaries may exfiltrate data, such as sensitive documents, through the use of automated processing after being gathered during Collection.

Evidence: 2026-10-09/aa26-281a-integrity-tech-microscan-exchange-mail-theft · ATT&CK page ↗

T1567.002Exfiltration Over Web Service: Exfiltration to Cloud Storage×1

Adversaries may exfiltrate data to a cloud storage service rather than over their primary command and control channel. Cloud storage services allow for the storage, edit, and retrieval of data from a remote cloud storage server over the Internet.

Evidence: 2026-10-07/gentlemen-affiliate-azazel-ci-cd-secrets-mcp-attacks · ATT&CK page ↗

Impact TA0040

T1485Data Destruction×2

Adversaries may destroy data and files on specific systems or in large numbers on a network to interrupt availability to systems, services, and network resources. Data destruction is likely to render stored data irrecoverable by forensic techniques through overwriting files or data on local and remote drives. Common operating system file deletion commands such as <code>del</code> and <code>rm</code> often only remove pointers to files without wiping the contents of the files themselves, making the files recoverable by proper forensic methodology. This behavior is distinct from Disk Content Wipe and Disk Structure Wipe because individual files are destroyed rather than sections of a storage disk or the disk's logical structure.

Evidence: 2026-10-07/gentlemen-affiliate-azazel-ci-cd-secrets-mcp-attacks · 2026-08-19/cve-2026-19478-gitlab-graphql-unauth-data-destruction · ATT&CK page ↗

T1491.001Defacement: Internal Defacement×1

An adversary may deface systems internal to an organization in an attempt to intimidate or mislead users, thus discrediting the integrity of the systems. This may take the form of modifications to internal websites or server login messages, or directly to user systems with the replacement of the desktop wallpaper. Disturbing or offensive images may be used as a part of Internal Defacement in order to cause user discomfort, or to pressure compliance with accompanying messages. Since internally defacing systems exposes an adversary's presence, it often takes place after other intrusion goals have been accomplished.

Evidence: 2026-10-07/gentlemen-affiliate-azazel-ci-cd-secrets-mcp-attacks · ATT&CK page ↗

Entries about GitLab (5)

2026-10-13 · view entry permalink →

HIGHCVE-2026-97229updatedNATOA2

CVE-2026-97229, GitLab CE/EE: an integer overflow in the CI/CD regular-expression compiler allows code execution on self-managed servers and now has a public proof of concept; fixed in 19.4.2, 19.3.5 and 19.2.8, and 19.4.1 does not close it (CVSS 10.0)

GitLab's critical patch release of 2026-10-12 (19.4.2, 19.3.5 and 19.2.8) fixes CVE-2026-97229, an integer overflow in the CI/CD regular-expression compiler that, "under certain conditions", could allow an unauthenticated user to execute arbitrary code on the GitLab server through a specially crafted regular expression in a CI/CD configuration; GitLab scores it CVSS 3.1 10.0 with no privileges required (GitLab, 2026-10-12). Affected are self-managed CE and EE from 19.2 before 19.2.8, 19.3 before 19.3.5 and 19.4 before 19.4.2; GitLab.com already runs the patched version and Dedicated customers need no action (GitLab, 2026-10-12). CERT-EU and BleepingComputer give 19.3.4 as the 19.3 fix, but GitLab's page names 19.3.5 and says 19.3.4 had a merge-request page bug, so the GitLab figure governs (CERT-EU, 2026-10-12; BleepingComputer, 2026-10-12). The 19.4.1 release of 2026-09-23 fixed two flaws from the same reporter in the same component, a double free in the regular-expression parser and an integer overflow in the compiler, both rated for an authenticated user (GitLab, 2026-09-23); CVE-2026-97229 is rated without that requirement, and 19.4.1 is still affected. NCSC Switzerland and CERT-EU both published advisories on 2026-10-12 (NCSC Switzerland, 2026-10-12; CERT-EU, 2026-10-12); NCSC lists the exploitation status as unknown (NCSC Switzerland, 2026-10-12); Rapid7 reproduced the code execution on 19.4.1, published a proof of concept, and reports no confirmed exploitation in the wild (Rapid7, 2026-10-13). GitLab publishes the issue detail for a security fix 90 days after the release that carries it (GitLab, 2026-10-12).

Triage: ordinary CI jobs run shells under the runners; only a shell spawned by the GitLab application server processes themselves matches this flaw, not one started inside a runner job; an anonymous CI lint request is ordinary on its own, and the signal is one aimed at a project that a newly created or little-used account has just pushed a CI configuration to.

GitLab has remediated an issue 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.

all versions from 19.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

GitLab (Critical Patch Release 19.4.2, 19.3.5, 19.2.8) 2026-10-12

Network access to an affected self-managed instance and delivery of a crafted regular expression through CI/CD configuration

NCSC Switzerland (Security Hub advisory) 2026-10-12

CERT-EU strongly recommends upgrading self-managed GitLab CE/EE instances to a fixed version as soon as possible, starting with internet-facing instances.

CERT-EU 2026-10-12

As of this writing, there is no confirmed in-the-wild exploitation of CVE-2026-97229.

Rapid7's testing found that an attacker must first be able to commit a malicious CI/CD configuration file .gitlab-ci.yml, and a repository path containing UTF-8 characters to a branch in a public project.

Rapid7 2026-10-13

An attacker with permission to push to a public project supplies a CI regular expression and a specially named path.

Rapid7 researcher repository (proof-of-concept README) 2026-10-13
Updaterun 2026-10-14T0255Z-inteltitleheadlinesummarytagscvessourcesevidencesourcing_noteactionsbody

Rapid7 reports that it independently reproduced arbitrary code execution on the official GitLab CE 19.4.1 image with address space layout randomization enabled, that the same input did not execute on the patched 19.4.2 image, and that it found no confirmed exploitation in the wild (Rapid7, 2026-10-13). Its testing shows the unauthenticated label needs a qualifier: the attacker must first push a malicious CI/CD configuration and a UTF-8 repository path to a branch in a public project, which an ordinary account can do where users may create public projects (Rapid7, 2026-10-13); the proof of concept then triggers it with a request without credentials (Rapid7 proof-of-concept README, 2026-10-13). A proof of concept went public the same day; its README says the included offsets were tested only against the 19.4.1 CE Linux amd64 image, that other builds need adjusted offsets, and that the generated payload is slightly larger than 2 GiB, needing about 9 GiB of memory on the test host (Rapid7 proof-of-concept README, 2026-10-13). The affected and fixed versions are unchanged.

vulnerability13 Oct 03:42Zmulti-sourceOpen finding →

2026-09-12 · view entry permalink →

HIGHCVE-2026-85706 +2exploitedupdatedNATOA1

CVE-2026-85706, GitLab CE/EE: unauthenticated path traversal in the repository commits API reads arbitrary server files, and honeypots recorded probes by the day after the patch (CVSS 10.0)

GitLab's own patch-release notes name the root cause plainly: "improper path confinement and missing authentication enforcement in the repository commits API" let an unauthenticated caller read arbitrary files from the server (GitLab, 2026-09-10). The vulnerability, CVE-2026-85706 (CVSS 10.0, scope-changed, no privileges or user interaction required), affects every self-managed CE/EE release from 18.7 up to 19.1.8, 19.2.6 and 19.3.2, the versions GitLab shipped on 2026-09-10, with backports to 19.0.9 and 18.11.12 following on 2026-09-23; GitLab.com was already running the patched version, and GitLab Dedicated customers need no action. watchTowr warns that the readable files can include configuration files, secrets or other sensitive server-side data, and that GitLab instances often hold source code, credentials and CI/CD configuration data (watchTowr, 2026-09-11); in analyst judgement, that is what turns a file-read primitive into a foothold on the CI/CD and source-control plane GitLab manages. The flaw was reported through GitLab's HackerOne bug-bounty program by researcher s3ntago (GitLab, 2026-09-10).

watchTowr reproduced the vulnerability and validated exposure across client environments, and by 2026-09-11 its Attacker Eye honeypot network was already recording behavioral probes for the vulnerability, which watchTowr reads as attackers having already built an exploit (watchTowr, 2026-09-11). CISA added the CVE to its Known Exploited Vulnerabilities catalog on 2026-09-11 (CISA KEV, catalogue version 2026.09.11), and NCSC Switzerland's own advisory, published earlier that same day, still recorded exploitation status as "unknown", which shows how fast the status moved within a single day (NCSC Switzerland, 2026-09-11). The same release also fixed CVE-2026-87719 (CVSS 9.9), an insecure GraphQL-subscription deserialization issue that lets an authenticated user with Duo Chat access obtain Advanced Search configurations and credentials (GitLab, 2026-09-10); it is not KEV-listed, and NCSC Switzerland's advisory has since recorded it as exploited too (see the 2026-09-16 update below), though on materially thinner evidence than CVE-2026-85706's own KEV listing and honeypot corroboration.

GitLab has remediated an issue that, under certain conditions, an unauthenticated user could have read arbitrary files from the GitLab server due to improper path confinement and missing authentication enforcement in the repository commits API.

GitLab

watchTowr Intel is already seeing behavioral probes for this vulnerability against Attacker Eye, our global honeypot network, meaning attackers have already successfully reverse engineered and reproduced the vulnerability and the countdown to indiscriminate, in-the-wild exploitation is on.

Defenders should also hunt through log files for HTTP POST requests to “/api/v4/projects/{id}/repository/commits/” URIs containing “file.path” parameters to identify potential exploitation attempts.

watchTowr 2026-09-11

CVE-2026-87719 is known as actively exploited

Actively exploited, Proof of Concept available

NCSC Switzerland, Cyber Security Hub (CSH), 2026-09-14/15 edits 2026-09-15
Updaterun 2026-09-13T0409Z-intelcvestagsbody

NCSC Switzerland's own advisory, published 2026-09-11, independently confirms CVE-2026-87719 (CVSS 9.9, GitLab EE only) alongside CVE-2026-85706 in the same posting. GitLab's own release notes describe the flaw: "GitLab has remediated an issue that, under certain conditions, could allow an authenticated user with Duo Chat access to obtain Advanced Search instance configurations and sensitive credentials using a specially crafted GraphQL subscription argument to bypass serialization and perform server object lookup" (GitLab, 2026-09-10). Affected versions are EE only, 18.3 up to the same 19.1.8/19.2.6/19.3.2 fixed releases named above; no exploitation is confirmed for this CVE. The same release also fixed CVE-2026-88765 (CVSS 8.5, GitLab EE only, sourced from GitLab's own release notes alone with no independent confirmation found): "GitLab has remediated an issue that, under certain conditions, could allow an authenticated user to achieve remote code execution by importing a specially crafted Git project export to overflow the Unicode conversion buffer used in Advanced Search indexing" (GitLab, 2026-09-10). This flaw's affected-version floor, EE 12.3, is substantially older than the other two flaws in this release, so any EE instance that has deferred upgrades for a long period carries the largest exposure window for this specific remote-code-execution path.

By inference from the mechanism, audit logs for GraphQL subscription requests with abnormal argument shapes targeting Advanced Search, and for an Advanced Search reindex operation immediately following a Git project import from an external or untrusted source, are the discriminators for these two additional flaws.

Updaterun 2026-09-16T0409Z-intelcvestagsactionssourcesevidencebody

NCSC Switzerland's Cyber Security Hub posting for this advisory was edited twice more inside this window. On 2026-09-14 the posting's own edit-history record states "CVE-2026-87719 is known as actively exploited" (NCSC Switzerland, 2026-09-14), moving the GitLab EE deserialization flaw from patch-available-only to exploited; that same-day posting carries no further detail on this CVE specifically (no campaign, no named cluster, no second source, and CISA's KEV catalog does not list it) so this status rests on NCSC Switzerland's own brief statement alone rather than the broader corroboration CVE-2026-85706 already carries. On 2026-09-15 the same posting was updated again, its status field now reading "Actively exploited, Proof of Concept available" for CVE-2026-85706 (NCSC Switzerland, 2026-09-15), and linking a public working proof of concept whose repository dates from 2026-09-11 (guneykabel, 2026-09-11). No new affected-version information accompanies either update; GitLab 19.3.2/19.2.6/19.1.8 remain the fixed releases for both CVEs.

Any self-managed instance still unpatched should now be treated as likely already probed on both fronts: the file-read path with a public exploit script circulating, and, for any instance with Duo Chat-enabled accounts, the Advanced Search credential-exposure path CVE-2026-87719 opens.

Updaterun 2026-10-11T1307Z-auditcvessourcesbodysummaryactionstitleheadline

On 2026-09-23 GitLab released 19.0.9 and 18.11.12, backporting the fixes for CVE-2026-85706 and CVE-2026-87719 to self-managed installations that cannot immediately move to 19.1 or later (GitLab, 2026-09-23). Instances on 18.7 to 18.11 or on 19.0 are therefore fixed by 18.11.12 or 19.0.9 rather than only by an upgrade to a newer minor release. GitLab says these versions contain only those security fixes (GitLab, 2026-09-23), so GitLab EE on the backport trains stays exposed to CVE-2026-88765, which is fixed from 19.1.8 (GitLab, 2026-09-10). GitLab has published three detections for CVE-2026-85706 exploitation attempts: reads of gitlab.yml, inclusion through the metadata.path parameter, and file-path enumeration (GitLab, 2026-09-10). NCSC Switzerland's exploited status for CVE-2026-87719 rests on its post's edit history; the update text of the same day concerns CVE-2026-85706's KEV listing (NCSC Switzerland, 2026-09-15).

vulnerability12 Sep 04:09Zmulti-sourceOpen finding →

2026-10-09 · view entry permalink →

NOTABLECVE-2015-3306 +7exploitedNATOA2

AA26-281A: China-linked actors enabled by Integrity Technology Group scan with MicroScan, spray Exchange and Microsoft 365 passwords and steal mail, and five old flaws from the scanner's scripts enter CISA KEV

The FBI, CISA, NSA, NCSC UK and partners from Australia, Canada, Japan, New Zealand and Spain describe Integrity Technology Group as a China-based company with links to the Chinese government that builds and sells cyber tools, hosts infrastructure and compromises networks; the actors it enables use tactics consistent with Flax Typhoon, Ethereal Panda and Red Juliett, among others (FBI IC3, AA26-281A, 2026-10-08). The Justice Department says the FBI seized the domains of MicroScan and the FishHub phishing platform, both operated by Integrity Tech (U.S. Department of Justice, 2026-10-08). Victims include U.S. government services, other critical sectors and organisations in Southeast Asia, Africa and North America; the advisory names no Swiss victim (FBI IC3, AA26-281A, 2026-10-08).

The chain starts with open-source scanners and MicroScan, a Python-based web application of 1,300-plus scripts, used since at least 2017 (FBI IC3, AA26-281A, 2026-10-08). Initial access has mostly come since January 2021 from command-line exploit utilities, and additionally from a cross-site-scripting payload that overlays a login form and offers a ZIP holding an executable that starts a process named like the Windows DiagTrack service (FBI IC3, AA26-281A, 2026-10-08). The actors spray and guess passwords with the EBurst tool against Exchange and Microsoft 365 (ECP, EWS, OAB, OWA, RPC, API, MAPI, PowerShell, Autodiscover, ActiveSync) (FBI IC3, AA26-281A, 2026-10-08). Persistence is a SoftEther VPN client, often named conhost.exe or dllhost.exe, which endpoint tools are less likely to flag (FBI IC3, AA26-281A, 2026-10-08). Collection uses a PHP bot and a Linux utility that read mail through Exchange Web Services and Microsoft 365 with application client, tenant and secret values, and a DCSync tool that replicates directory data from a domain controller; mail was stolen from government, law-enforcement and healthcare bodies in Southeast Asia (FBI IC3, AA26-281A, 2026-10-08).

Appendix B lists eight successfully exploited CVEs recovered from MicroScan's scripts: ProFTPD 1.3.5, ISC BIND 9.x, Apache Struts 2.3.19 to 2.3.28, ONLYOFFICE DocumentServer 5.1.5 through 5.6.2 and Strapi up to 4.5.5, plus GNU Bash through 4.3, Pulse Connect Secure and GitLab from 11.9 (FBI IC3, AA26-281A, 2026-10-08); CISA added the first five to its catalogue on 2026-10-08 (CISA KEV catalogue, 2026-10-08). Apache names Struts 2.3.20.3, 2.3.24.3 and 2.3.28.1 as fixed (Apache Struts, 2021-02-13) and Strapi names 4.8.0 (Strapi, 2023-04-17).

Triage: conhost.exe and dllhost.exe are legitimate Windows names, so the file's path, signature and network behaviour separate a downloaded SoftEther client from the system binary (FBI IC3, AA26-281A, 2026-10-08).

The activity in the advisory is reported to be consistent with campaigns also publicly known as Flax Typhoon, Ethereal Panda and Red Juliett among others.

NCSC UK 2026-10-08

Integrity Tech has contracts with the PRC government.

U.S. Department of Justice 2026-10-08

Network defenders should include these interfaces when defending against EBurst.

FBI, CISA, NSA, NCSC UK and partners (joint advisory AA26-281A) 2026-10-08

Builds on: A PRC state-enablement platform leasing commercial proxy subscriptions as anonymisation…

threat09 Oct 03:43Zsingle-source · national CERTOpen finding →

Earlier coverage (2)

2026-10-07NOTABLEupdatedNATOB2A Gentlemen ransomware affiliate ran his own leak site and reached his victims through stolen CI/CD secrets, with attack commands driven through an MCP server (CloudSEK)CloudSEK analysed two exposed servers of "Azazel", a Russian-speaking affiliate of the Gentlemen ransomware group who also ran his own leak site, and reports about 6 TB of stolen data from some two dozen organisations, among them government-adjacent infrastructure. It says every victim outside one AI-platform intrusion was reached through stolen CI/CD secrets, mainly GitLab variable stores and git history, and that the deeper intrusion into an AI platform chained server-side request forgery, a recovered master key that decrypted the configuration and a token recovered from git history, and that Azazel drove attack commands through an MCP server on a local port. The report is a single source and names no victim.2026-08-19HIGHexploitedupdatedNATOA2CVE-2026-19478; GitLab ships an out-of-band critical patch for a GraphQL directive flaw that lets an unauthenticated caller modify or delete public projects and user data (CVSS 9.4)GitLab released 19.2.4, 19.1.6, 19.0.8 and 18.11.11 for Community and Enterprise Edition on 2026-08-17 outside its scheduled patch cadence, fixing CVE-2026-19478; a code-injection flaw reachable through a GraphQL directive that GitLab states can allow an unauthenticated user to remotely modify or delete public projects and user data, rated CVSS 9.4 with no authentication and no user interaction. Every release line from 18.2 onward is affected. GitLab.com and GitLab Dedicated were already patched at disclosure, so the exposure is entirely self-managed instances. A companion CSRF flaw in the GraphQL multiplex query handler, CVE-2026-19650 at CVSS 7.1, lets mutations be executed through GET requests. No exploitation is reported by any party and GitLab withholds the technical detail for 90 days.

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Vulns3
  • Threats2

Source distribution

  • docs.gitlab.com5 (20%)
  • security-hub.ncsc.admin.ch3 (12%)
  • cert.ssi.gouv.fr2 (8%)
  • github.com2 (8%)
  • bleepingcomputer.com1 (4%)
  • cert.europa.eu1 (4%)
  • cisa.gov1 (4%)
  • cloudsek.com1 (4%)
  • other9 (36%)
All cited sources (25)