Threat Intelligence Database
Comprehensive database of the latest cyber threats affecting organizations worldwide. Filter and search to find specific threat intelligence relevant to your organization.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threat Intelligence
Click on any threat for detailed analysis and mitigation recommendations
0 CVE-2026-44471 is a high-severity vulnerability in gitoxide, a Rust implementation of git, affecting versions prior to 0.21.1. It allows a maliciously crafted git tree to write attacker-controlled symbolic links into any directory where the user has write permissions during checkout. This occurs due to improper handling of symlink creation order and path validation caching, which bypasses certain security checks. The vulnerability enables potential unauthorized file system modifications with high impact on confidentiality, integrity, and availability. A fix was introduced in version 0.21.1 to address this issue. No known exploits in the wild have been reported. Join the discussion | CVE Database V5 | 05/13/2026, 21:36:44 UTC Added: 05/13/2026, 21:51:29 UTC |
gitoxide is an implementation of git written in Rust. Before 0.42.0, gitoxide uses SHA-1 hash implementations without any collision detection, leaving it vulnerable to hash collision attacks.gitoxide uses the sha1_smol or sha1 crate, both of which implement standard SHA-1 without any mitigations for collision attacks. This means that two distinct Git objects with colliding SHA-1 hashes would break the Git object model and integrity checks when used with gitoxide. This vulnerability is fixed in 0.42.0. Join the discussion | CVE Database V5 | 04/04/2025, 14:41:56 UTC Added: 01/23/2026, 17:20:57 UTC |
Showing 1 to 2 of 2 results