WaratekVRT Sign in
Reset
More filters (1)
Columns
Including CVEs outside Waratek scope✕Product git✕
Overview 2,733 matches · 384 in Waratek scope · 21 protected · 37 exploited · 14 CISA KEV · 132 public PoC · 55 EPSS ≥ 0.5
2,733matches 384in Waratek scope14.1% 21protected0.8% 37exploited1.4% 14CISA KEV0.5% 132public PoC4.8% 55EPSS ≥ 0.52.0%
Protected by Waratek 21 0.8% Rule in development 1 0.0% Mitigation candidate 12 0.4% No exploit published 350 12.8% Outside Waratek scope 6 0.2% Not applicable 2,343 85.7% Withdrawn CVE 0 0.0%
Critical 273 10.0% High 869 31.8% Medium 1,488 54.4% Low 103 3.8% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 21 0.8% partly blocked 0 0.0% not blocked 2,712 99.2% not established 0 0.0% unrecorded 0 0.0%
Exploited 37 1.4% Working exploit published 89 3.3% Proof of concept only 252 9.2% Forecast only 13 0.5% No public exploit 2,342 85.7%
split by peak 423 / year
Not applicable: 2,343Outside Waratek scope: 6No exploit published: 350Mitigation candidate: 12Rule in development: 1Protected by Waratek: 21 Low: 103Medium: 1,488High: 869Critical: 273 not blocked: 2,712blocked by ARMR today: 21 No public exploit: 2,342Forecast only: 13Proof of concept only: 252Working exploit published: 89Exploited: 37
19981 Not applicable1 High1 not blocked1 No public exploit1 19990 20000 20011 Not applicable1 High1 not blocked1 No public exploit1 20024 Not applicable4 Medium3 Low1 not blocked4 Working exploit published1 No public exploit3 20031 Not applicable1 High1 not blocked1 Working exploit published1 20041 Not applicable1 High1 not blocked1 Working exploit published1 20057 Not applicable7 High3 Medium4 not blocked7 Working exploit published2 No public exploit5 20067 Not applicable7 High4 Medium3 not blocked7 Working exploit published4 No public exploit3 200712 Not applicable12 High7 Medium5 not blocked12 Exploited1 Working exploit published6 No public exploit5 200812 Not applicable12 High7 Medium5 not blocked12 Working exploit published7 No public exploit5 200917 Not applicable17 High7 Medium10 not blocked17 Working exploit published9 No public exploit8 201012 Not applicable12 High7 Medium5 not blocked12 Working exploit published5 No public exploit7 201110 Not applicable10 High4 Medium3 Low3 not blocked10 Working exploit published4 No public exploit6 20127 Not applicable7 High2 Medium5 not blocked7 No public exploit7 20136 Not applicable6 High1 Medium5 not blocked6 No public exploit6 201419 Not applicable19 High5 Medium14 not blocked19 Working exploit published5 No public exploit14 201522 Not applicable22 High5 Medium16 Low1 not blocked22 Working exploit published6 No public exploit16 201624 Not applicable24 Critical16 High4 Medium2 Low2 not blocked24 Working exploit published1 No public exploit23 201768 Protected by Waratek1 No exploit published4 Not applicable63 Critical15 High32 Medium20 Low1 blocked by ARMR today1 not blocked67 Exploited1 Working exploit published4 No public exploit63 2018109 Mitigation candidate1 No exploit published9 Not applicable99 Critical24 High40 Medium45 not blocked109 Exploited2 Working exploit published3 Proof of concept only1 Forecast only1 No public exploit102 2019251 Protected by Waratek2 No exploit published16 Outside Waratek scope1 Not applicable232 Critical24 High63 Medium158 Low6 blocked by ARMR today2 not blocked249 Exploited3 Working exploit published5 Proof of concept only1 No public exploit242 2020322 Protected by Waratek2 Mitigation candidate5 No exploit published21 Outside Waratek scope1 Not applicable293 Critical36 High102 Medium178 Low6 blocked by ARMR today2 not blocked320 Exploited4 Working exploit published6 Proof of concept only3 Forecast only1 No public exploit308 2021241 Protected by Waratek3 No exploit published32 Outside Waratek scope1 Not applicable205 Critical18 High67 Medium145 Low11 blocked by ARMR today3 not blocked238 Exploited4 Working exploit published2 Proof of concept only1 Forecast only3 No public exploit231 2022269 Protected by Waratek6 Mitigation candidate2 No exploit published40 Not applicable221 Critical35 High72 Medium155 Low7 blocked by ARMR today6 not blocked263 Exploited2 Working exploit published11 Proof of concept only27 Forecast only3 No public exploit226 2023274 Protected by Waratek1 Mitigation candidate1 No exploit published31 Outside Waratek scope1 Not applicable240 Critical31 High81 Medium154 Low8 blocked by ARMR today1 not blocked273 Exploited7 Working exploit published3 Proof of concept only112 Forecast only4 No public exploit148 2024232 Protected by Waratek1 Mitigation candidate1 No exploit published46 Not applicable184 Critical31 High64 Medium128 Low9 blocked by ARMR today1 not blocked231 Exploited4 Proof of concept only15 Forecast only1 No public exploit212 2025381 Protected by Waratek4 Rule in development1 Mitigation candidate2 No exploit published140 Not applicable234 Critical10 High112 Medium242 Low17 blocked by ARMR today4 not blocked377 Exploited2 Working exploit published3 Proof of concept only28 No public exploit348 2026423 Protected by Waratek1 No exploit published11 Outside Waratek scope2 Not applicable409 Critical33 High176 Medium183 Low31 blocked by ARMR today1 not blocked422 Exploited7 Proof of concept only64 No public exploit352
1999200220052008201120142017202020232026
2,733 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed. ‹ prev page 2 of 28 next ›
CVE Severity Published▾ Status Exploitation Description
CVE-2024-11222 Medium 2026-09-16 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.0 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that under certain conditions could have allowed a developer user to perform actions in the context of another user's merge request commit due to a race condition issue in pipeline creation.
CVE-2026-88765 High 2026-09-15 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 12.3 to 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 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.
CVE-2026-82837 Medium 2026-09-15 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.1.0 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that certain conditions could have allowed an authenticated user to access sensitive credentials and tokens without transiting the expected proxy due to improper authorization checks on internal data emission endpoints.
CVE-2026-13210 High 2026-09-15 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that under certain conditions could have allowed an authenticated user to access CI/CD variables outside their intended environment scope due to improper input validation in the environment scope pattern matcher.
CVE-2026-12910 Medium 2026-09-15 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.6 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that under certain conditions could have allowed an authenticated user to bypass SAML SSO sign-in restrictions and authenticate without SSO due to missing authentication enforcement checks.
CVE-2026-87719 Critical 2026-09-12 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 18.3 before 18.11.12, 19.0 before 19.0.9, 19.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 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.
CVE-2026-85706 Critical 2026-09-12 Not applicable Exploited GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 18.11.12, 19.0 before 19.0.9, 19.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 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.
CVE-2026-87819 High 2026-09-09 Not applicable No public exploit GitPython before 3.1.60 contains a regular expression denial of service vulnerability in Actor.name_email_regex that processes commit author and committer fields. Attackers can craft a commit object with a malformed author field containing an unterminated angle bracket to cause quadratic backtracking, exhausting CPU resources for over two minutes per commit access.
CVE-2026-87818 High 2026-09-09 Not applicable Proof of concept only GitPython 3.1.59 fails to restrict the --no-index option in the high-level diff API, allowing attackers to read arbitrary filesystem paths as repository operands. Attackers can combine --no-index with -I/--ignore-matching-lines to create a content-dependent Boolean oracle, repeatedly querying local files to recover single-line secrets through distinguishable success or error responses.
CVE-2026-87817 High 2026-09-09 Not applicable No public exploit GitPython before 3.1.60 fails to properly validate the git directory location, allowing attackers to impersonate the git directory using tracked files like gitdir, commondir, and HEAD. Attackers can execute arbitrary code by placing a malicious pre-commit hook in the tracked hooks directory that executes when a victim calls index.commit() on a cloned or opened repository.
CVE-2026-81166 Medium 2026-09-02 Not applicable No public exploit Missing Authorization vulnerability in Drupal Digital Signage Framework allows Forceful Browsing. This issue affects Digital Signage Framework versions: from 0.0.0 to 2.6.1.
CVE-2026-75871 Critical 2026-08-27 Not applicable Proof of concept only GitLab has remediated a vulnerability in the GitLab AI Gateway component affecting all versions of the AI Gateway from 18.10 to 19.0.12, 19.1 to 19.1.7, and 19.2 to 19.2.2 that could have allowed an authenticated user with Duo Agent Platform access to redirect outbound model requests to an externally-controlled endpoint via a crafted inline flow configuration that overrides the HTTP Host header, resulting in disclosure of Google Cloud Vertex cloud service credentials and private signing keys.
CVE-2026-77801 Medium 2026-08-26 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.8 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, could have allowed an authenticated user to cause a denial of service affecting background job processing, due to missing object count limits.
CVE-2026-7487 Low 2026-08-26 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 13.1 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user with reporter-role permissions who authored a merge request could have reset merge request approval rules due to improper authorization checks.
CVE-2026-60004 Critical 2026-08-26 Not applicable Exploited Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation.
CVE-2026-3035 Medium 2026-08-26 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 11.3 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user with project Maintainer permissions could have accessed the terminal of a protected environment they were not authorized to use due to improper authorization checks.
CVE-2026-18252 High 2026-08-26 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 18.9 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user with developer-role permissions could have executed arbitrary commands in a CI context, due to the Claude agent processing configuration from a user-controlled source.
CVE-2026-15387 Medium 2026-08-26 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user with developer-role permissions could have influenced the execution environment of Pipeline Execution Policy enforcement jobs, due to improper handling of job dependencies.
CVE-2025-10903 Medium 2026-08-26 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 11.10 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user could have caused denial of service, due to an unbounded loop triggered by specially crafted input in the SCIM user provisioning feature.
CVE-2026-78678 High 2026-08-25 Not applicable Proof of concept only GitPython versions before 3.1.59 contain an incomplete denylist in the unsafe_git_revision_options guard that omits --contents and -S options, allowing attackers to read arbitrary files by passing these options to Repo.blame(). Attackers can supply revision values like --contents=/etc/passwd to leak file contents through the blame result returned to the caller.
CVE-2026-78677 High 2026-08-25 Not applicable Proof of concept only GitPython before 3.1.59 omits --separate-git-dir from unsafe_git_clone_options, allowing attackers to create arbitrary git directories outside the intended clone destination. Attackers can pass a separate_git_dir parameter to Repo.clone_from() or Repo.clone() to redirect repository metadata to an attacker-controlled filesystem path, enabling arbitrary directory creation and potential hook execution.
CVE-2026-78676 Critical 2026-08-25 Not applicable No public exploit GitPython before 3.1.59 fails to safely re-serialize multi-line git-config values during write operations, corrupting dormant quoted values into injected directives like core.hooksPath. Attackers can craft config files with embedded newlines that become live git directives after any unrelated GitPython config write, enabling arbitrary code execution via hook invocation.
CVE-2026-78675 High 2026-08-25 Not applicable Proof of concept only GitPython before 3.1.59 fails to disable merge_includes when parsing .gitmodules, allowing attackers to disclose local file content by including arbitrary file paths via [include] directives. Attackers can craft a malicious .gitmodules file with include directives pointing to sensitive files; when repo.submodules is accessed, GitConfigParser raises MissingSectionHeaderError embedding the target file's first line verbatim in the exception message.
CVE-2026-10053 High 2026-08-23 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.8 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user to achieve remote code execution due to a path traversal vulnerability in the package registry.
CVE-2026-76222 High 2026-08-19 Not applicable Proof of concept only GitPython before 3.1.58 fails to validate submodule names from .gitmodules files, allowing attackers to create Git repositories at arbitrary filesystem paths outside the intended clone directory. Attackers can craft malicious repositories with traversal sequences in submodule names that GitPython processes during submodule initialization, creating attacker-controlled Git repositories at escaped filesystem locations.
CVE-2026-76221 High 2026-08-19 Not applicable No public exploit GitPython before 3.1.58 contains a config-name injection vulnerability in the option-name validator that allows attackers to forge arbitrary git-config directives by injecting equals signs, hash symbols, and whitespace into option names. Attackers can inject malicious option names like 'sshCommand = touch /tmp/RCE #' to execute arbitrary commands via core.sshCommand or core.hooksPath on the next git operation.
CVE-2026-76220 High 2026-08-19 Not applicable No public exploit GitPython before 3.1.58 contains a command execution vulnerability in the check_unsafe_options guard that can be bypassed by combining a single-character kwarg with split_single_char_options=False. Attackers can supply a crafted kwargs dictionary to guarded methods like clone_from to emit a joined token parsed as --upload-pack, enabling arbitrary OS command execution at default allow_unsafe_options=False.
CVE-2026-76219 High 2026-08-19 Not applicable No public exploit GitPython versions before 3.1.58 contain an arbitrary file overwrite vulnerability in IndexFile.from_tree, IndexFile.reset, and IndexFile.merge_tree methods that append caller-influenced treeish strings to git read-tree without option validation or argument separation. Attackers can inject the --index-output option to overwrite arbitrary files with a valid git-index blob, destroying existing file content at attacker-controlled writable paths.
CVE-2026-76218 High 2026-08-19 Not applicable No public exploit GitPython before 3.1.58 contains a remote code execution vulnerability in Repo.init that forwards unsafe git options without validation. Attackers can supply a template parameter pointing to a directory with malicious git hooks that execute arbitrary code when git operations are performed on the initialized repository.
CVE-2026-76217 High 2026-08-19 Not applicable Proof of concept only GitPython versions before 3.1.58 fail to validate options passed to git rm and git checkout commands in IndexFile.remove() and Head.checkout(). Attackers can supply --pathspec-from-file and --pathspec-file-nul parameters to read arbitrary files accessible to the process, with full file contents returned in GitCommandError.stderr.
CVE-2026-19650 High 2026-08-17 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, and 19.2 before 19.2.4 that under certain conditions could have allowed an unauthenticated user to execute mutations via GET requests due to improper request validation in GraphQL multiplex query handling.
CVE-2026-19478 Critical 2026-08-17 Not applicable Exploited GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, and 19.2 before 19.2.4 that under certain conditions could allow an unauthenticated user to remotely modify or delete public projects and user data via a GraphQL directive.
CVE-2026-73625 High 2026-08-13 Not applicable No public exploit GitPython versions before 3.1.54 contain a remote code execution vulnerability in the check_unsafe_options guard that can be bypassed by smuggling git options inside single-character kwarg values. Attackers can supply crafted option dictionaries to clone_from, fetch, pull, push, ls_remote, iter_commits, blame, or archive methods to execute arbitrary OS commands via the --upload-pack parameter.
CVE-2026-73624 High 2026-08-13 Not applicable Proof of concept only GitPython versions before 3.1.54 contain an arbitrary file overwrite vulnerability in the Diffable.diff method that fails to validate git options passed through kwargs. Attackers can supply the --output argument via the other parameter or output kwarg to write patch content to attacker-chosen file paths at process privilege level.
CVE-2026-73623 High 2026-08-13 Not applicable Proof of concept only GitPython before 3.1.54 contains an incomplete denylist in unsafe_git_clone_options that omits --template, allowing attackers to achieve arbitrary command execution during clone operations. Attackers can supply --template pointing to a directory containing malicious post-checkout hooks that execute when git clones the repository.
CVE-2026-73622 High 2026-08-13 Not applicable Proof of concept only GitPython before 3.1.55 fails to disable environment variable expansion in Remote.create() and Submodule.add() URL handling, allowing attackers to exfiltrate secrets by supplying URLs containing variable references. Attackers can craft URLs with environment variable tokens that are expanded into .git/config and .gitmodules, then transmitted to attacker-controlled hosts during fetch or pull operations.
CVE-2026-73621 Medium 2026-08-13 Not applicable No public exploit GitPython before 3.1.56 contains an argument injection vulnerability in the Commit.count() method, which forwards keyword arguments to 'git rev-list' without the check_unsafe_options guard present in the sibling iter_items method. An attacker who can control options passed to Commit.count (e.g., via an application that forwards a user-supplied options dict) can supply output=<path>, causing 'git rev-list --output=<path>' to open and truncate the target file to zero bytes before revision parsing. This allows destruction/blanking of an arbitrary file at the process's privilege level (no content control, 0-byte truncation).
CVE-2026-73620 High 2026-08-13 Not applicable Proof of concept only GitPython before 3.1.57 fails to guard git option forwarding in IndexFile.checkout() and TagReference.create(), allowing attackers to pass unsafe options via kwargs. Attackers can use --prefix to overwrite arbitrary files with repository content or -F to read arbitrary files returned in-band.
CVE-2026-73619 High 2026-08-13 Not applicable Proof of concept only GitPython before 3.1.57 contains an incomplete denylist in the unsafe_git_archive_options guard that omits --add-file and --add-virtual-file options. Attackers can supply these options to Repo.archive() to read arbitrary files from the filesystem and include them in the returned archive.
CVE-2026-8667 Medium 2026-08-12 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.6 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user with developer role to modify certain package registry metadata without the required maintainer-level permissions due to improper authorization checks.
CVE-2026-7427 High 2026-08-12 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.5 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed an unauthenticated user to cause a denial of service due to improper input validation.
CVE-2026-6821 Medium 2026-08-12 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 12.0 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user to bypass IP-based access restrictions and read limited merge request information from a private project due to missing authorization checks in a merge requests API endpoint.
CVE-2026-4879 Medium 2026-08-12 Not applicable Proof of concept only GitLab has remediated an issue in GitLab EE affecting all versions from 16.0 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to view external status check configuration restricted to higher-privileged roles due to missing authorization on a merge request API endpoint.
CVE-2026-19228 High 2026-08-12 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.4 and 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user to cause AI usage to be attributed to another namespace, due to improper authorization of identity information supplied in requests.
CVE-2026-18433 Medium 2026-08-12 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.4 and 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user to read policy configuration belonging to a namespace they were not authorized to access, due to incorrect authorization checks in a GraphQL query.
CVE-2026-18244 Medium 2026-08-12 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 17.7 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user to view restricted configuration settings due to improper authorization checks on a group settings page.
CVE-2026-16627 Critical 2026-08-12 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to escalate privileges due to improper sanitization of HTML content rendered in a CI job modal.
CVE-2026-16494 High 2026-08-12 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.4 and 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user to modify project settings restricted to higher-privileged roles, due to missing authorization checks on a project update endpoint.
CVE-2026-15423 High 2026-08-12 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.0 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to execute CI/CD pipelines on a protected branch without the required push permissions due to improper authorization in pipeline reference validation.
CVE-2026-15217 High 2026-08-12 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed cross-site scripting due to improper neutralization of user-controlled values rendered in table cell content by an analytics dashboard component.
CVE-2026-15216 High 2026-08-12 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed cross-site scripting due to improper neutralization of user-controlled data rendered in pagination controls by an analytics dashboard component.
CVE-2025-9486 Low 2026-08-12 Not applicable Proof of concept only GitLab has remediated an issue in GitLab EE affecting all versions from 15.6 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed a user with a pending membership to receive permissions granted by a custom role, due to incorrect privilege assignment that did not account for membership state.
CVE-2026-65675 High 2026-08-11 Not applicable No public exploit No cwe for this issue in Visual Studio Code CoPilot Chat Extension allows an unauthorized attacker to bypass a security feature over a network.
CVE-2026-25292 High 2026-08-04 Not applicable No public exploit Memory Corruption when processing untrusted user input in the fastboot command handler for audio framework configuration.
CVE-2026-25289 Critical 2026-08-04 Not applicable No public exploit Memory Corruption when processing Device Capability Extended attributes in certain NAN Service Discovery Frames with invalid length values.
CVE-2026-21366 High 2026-08-04 Not applicable No public exploit Memory corruption while processing a packet with a size close to the maximum allowed value.
CVE-2026-69097 High 2026-08-03 Not applicable Proof of concept only GitPython before 3.1.53 fails to properly escape section names in git config files, allowing attackers to inject arbitrary configuration directives through malicious submodule names. Attackers can inject core.sshCommand or other dangerous config keys into the victim's .git/config via create_submodule or clone_from operations, achieving remote code execution when git performs ssh operations.
CVE-2026-67326 High 2026-08-01 Not applicable Proof of concept only GitPython before 3.1.50 fails to validate newline characters in the section parameter of config_writer(), allowing attackers to inject arbitrary section headers into .git/config. Attackers can inject newlines to create a forged [core] section with hooksPath pointing to attacker-controlled directories, achieving remote code execution when git hooks are triggered.
CVE-2026-67325 High 2026-08-01 Not applicable Proof of concept only GitPython before 3.1.51 contains an incomplete command injection blocklist that fails to account for git's long-option prefix abbreviation feature. Attackers can bypass the unsafe options guard by using abbreviated option names like upload_p instead of upload_pack, which git resolves to dangerous options and executes arbitrary commands.
CVE-2026-67324 Critical 2026-08-01 Not applicable No public exploit GitPython 3.1.50 fails to recognize joined short-option forms such as -u<value> (the short form of --upload-pack=<value>) when enforcing its default unsafe-option gate. When an application passes attacker-influenced clone options into Repo.clone_from(..., multi_options=..., allow_unsafe_options=False), an attacker can supply -u<helper> to bypass the gate that blocks --upload-pack/-u, causing Git to execute the specified helper command during clone. Fixed in 3.1.51.
CVE-2026-67323 High 2026-08-01 Not applicable Proof of concept only GitPython before 3.1.51 fails to guard against dangerous Git options passed as keyword arguments in Repo.archive() and git.ls_remote(), allowing command injection via options such as --exec/--upload-pack (leading to arbitrary command execution). Additionally, Repo.iter_commits() and Repo.blame() do not check for leading-dash revision arguments, so a revision like --output=<path> can cause Git to open and truncate an arbitrary file. Exploitation requires an application that passes attacker-controlled arguments to these methods.
CVE-2026-67322 High 2026-08-01 Not applicable Proof of concept only GitPython before 3.1.52 is vulnerable to environment-variable exfiltration in Repo.clone_from(). The caller-supplied remote URL is passed through Git.polish_url(), which on non-Cygwin platforms calls os.path.expandvars() on the URL before invoking git clone. An attacker who controls the clone URL can embed $NAME or ${NAME} tokens that are expanded to the values of the hosting process's environment variables (e.g., AWS_SECRET_ACCESS_KEY or GITHUB_TOKEN). The resulting URL, now containing the secret, is transmitted over the network to an attacker-controlled host during the clone attempt, disclosing the secret.
CVE-2026-6336 Medium 2026-07-29 Not applicable Proof of concept only GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.6 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an unauthorized user to view project import source information due to a missing authorization check.
CVE-2026-6267 High 2026-07-29 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.1.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an authenticated user with Developer role to access unauthorized information due to insufficient access controls on internal request handling.
CVE-2026-4672 Medium 2026-07-29 Not applicable Proof of concept only GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.4 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an authenticated user with guest-role permissions to access test report contents they were not authorized to view due to improper access control enforcement.
CVE-2026-3093 Medium 2026-07-29 Not applicable Proof of concept only GitLab has remediated an issue in GitLab CE/EE affecting all versions from 14.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an attacker to execute arbitrary JavaScript in another user's browser via a crafted URL, due to improper sanitization of user-controlled input.
CVE-2026-16553 Medium 2026-07-29 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 18.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed some sensitive information to be disclosed to an unintended host due to improper handling of upstream requests in virtual registries.
CVE-2026-15975 High 2026-07-29 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 11.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an unauthenticated user to cause a denial of service due to insufficient resource throttling when processing merge request discussions.
CVE-2026-15831 Medium 2026-07-29 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.3 and 19.2 before 19.2.1 that under certain conditions could have allowed an authenticated user to bypass administrator-configured tool governance policies due to improper authorization enforcement during token generation.
CVE-2026-15077 Medium 2026-07-29 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.3 and 19.2 before 19.2.1 that under certain conditions could have allowed an authenticated user to access information from unauthorized projects due to improper neutralization of untrusted content processed by the AI-assisted code review functionality.
CVE-2026-14351 Medium 2026-07-29 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 8.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an unauthenticated user to view the title of a confidential issue through a publicly accessible merge request due to improper authorization checks.
CVE-2026-14341 Medium 2026-07-29 Not applicable Proof of concept only GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an authenticated user with Maintainer role to modify protected branch configuration due to improper authorization in a projects API endpoint.
CVE-2026-13113 Medium 2026-07-29 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 17.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an authenticated user to merge code into a protected branch without the required approvals due to a race condition in approval rule processing.
CVE-2026-12436 High 2026-07-29 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an authenticated user to modify CI/CD configuration belonging to another user due to improper validation of user-supplied attributes when processing pipeline schedule inputs.
CVE-2025-14562 Low 2026-07-29 Not applicable Proof of concept only GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.6 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an authenticated user with developer-role permissions to commit changes to a project after being removed as a member, due to improper authorization checks on merge request collaboration settings.
CVE-2026-50510 High 2026-07-14 Not applicable No public exploit Improper restriction of names for files and other resources in Github Copilot allows an unauthorized attacker to execute code locally.
CVE-2026-58065 High 2026-07-13 Not applicable No public exploit The Apache Airflow Git provider runs its git-over-SSH operations with `StrictHostKeyChecking=no` by default, disabling SSH host-key verification. An attacker who can intercept the network path between an Airflow worker and the Git server can impersonate the server (man-in-the-middle), capturing the SSH deploy key or injecting malicious repository content. Deployments that use the Git DAG bundle or Git provider to clone over SSH with a deploy key are affected. The fix changes the default to verify host keys; upgrade to apache-airflow-providers-git `0.4.1` or later and configure a `known_hosts` file.
CVE-2026-8472 Medium 2026-07-08 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 18.9 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user with minimal access permissions to read work item metadata from private projects due to missing authorization checks.
CVE-2026-7492 Medium 2026-07-08 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 9.1 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an unauthenticated user to determine the existence of a private project due to improper authorization controls on cross-project reference pages.
CVE-2026-6896 High 2026-07-08 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 13.11 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to execute arbitrary scripts in another user's browser session due to improper sanitization of user-supplied input.
CVE-2026-6352 Low 2026-07-08 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 18.2 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user with auditor-level access to modify compliance violation records due to improper authorization on certain GraphQL operations.
CVE-2026-54528 High 2026-07-08 Not applicable Proof of concept only JupyterLab Git is a Git extension for JupyterLab. Prior to 0.54.0, jupyterlab-git uses fnmatch.fnmatchcase() in GitHandler.prepare() in jupyterlab_git/handlers.py to enforce excluded_paths, allowing an authenticated user on a case-insensitive filesystem to vary URL path casing and read excluded directories. This issue is fixed in version 0.54.0.
CVE-2026-54527 Critical 2026-07-08 Not applicable Proof of concept only JupyterLab Git is a Git extension for JupyterLab. From 0.30.0b3 before 0.54.0, the PlainTextDiff.ts createHeader() method passes Git filenames directly to innerHTML when rendering renamed files in commit history, allowing a crafted filename to execute JavaScript when a victim views the rename diff in the Git History tab. This issue is fixed in version 0.54.0.
CVE-2026-13320 High 2026-07-08 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.7 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user to execute arbitrary scripts in another user's browser session due to improper sanitization of user-supplied input.
CVE-2026-11827 Medium 2026-07-08 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 9.5 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user with maintainer-role permissions to obtain another user's stored credentials due to improper authorization controls.
CVE-2025-12506 Medium 2026-07-08 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.5 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user to create a repository where the content displayed in the web interface differed from the content available for download, due to improper handling of Git reference name resolution.
CVE-2026-21384 Medium 2026-07-06 Not applicable No public exploit Memory Corruption when updating prepared commands with invalid port indices based on user space input exceeds supported read client limits.
CVE-2026-21383 High 2026-07-06 Not applicable No public exploit Cryptographic Issue when using a static initialization vector for AES-GCM key wrapping, which requires a unique value for each call to ensure security.
CVE-2026-21370 Medium 2026-07-06 Not applicable No public exploit Memory Corruption when validating input batch size and buffer plane count exceeds maximum allowed values.
CVE-2026-21369 Medium 2026-07-06 Not applicable No public exploit Memory Corruption when handling flash commands due to outdated LED count values being used after userspace modification.
CVE-2026-21368 Medium 2026-07-06 Not applicable No public exploit Memory Corruption when parsing jpeg commands due to unaccounted extra writes to the buffer during validation checks.
CVE-2026-8330 Medium 2026-06-25 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 9.3 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed sensitive information to be written to application logs due to insufficient filtering in a CI/CD API endpoint.
CVE-2026-5952 Medium 2026-06-25 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.11 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an authenticated user with developer-role permissions to bypass package protection rules and overwrite protected Maven package metadata due to incorrect authorization checks.
CVE-2026-5796 Medium 2026-06-25 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.6 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an authenticated user with Reporter-level group permissions to view package metadata from projects with the Package Registry disabled due to incorrect authorization checks in the group packages feature.
CVE-2026-5309 Medium 2026-06-25 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 18.6 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an authenticated user to read or modify another group's virtual registry cleanup policy settings without authorization.
CVE-2026-3176 Low 2026-06-25 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 18.6 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an authenticated user with limited permissions to access project information due to insufficient authorization checks.
CVE-2026-2238 Medium 2026-06-25 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.5 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an unauthenticated user to view confidential issue references on public projects due to improper authorization checks.
CVE-2026-1606 Medium 2026-06-25 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 14.8 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an authenticated user to conceal content within a Snippet due to improper input validation.
CVE-2026-12635 Low 2026-06-25 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 8.3 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an authenticated user with maintainer-role permissions to make requests to internal network resources through mirror synchronization due to improper URL validation.
CVE-2026-12053 High 2026-06-25 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.1 that under certain conditions could have allowed a user to access sensitive information that had already been committed to a project, due to insufficient output filtering in Duo Workflows.
‹ prev page 2 of 28 next ›