Skip to main content

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.

Pro Console Lifetime

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)

View Plans & Pricing

API access activates after upgrading in Console -> Billing.

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now

Filter Threats

Narrow down the results by type, severity, or affected countries

Search threats by title, CVE ID, or description. Maximum 100 characters.
Active filters (1):Package: pkg:cargo/github/GitoxideLabs/gitoxide

Threat Intelligence

Click on any threat for detailed analysis and mitigation recommendations

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

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

Showing 1 to 2 of 2 results

Filters:Package: pkg:cargo/github/GitoxideLabs/gitoxide
Page 1 of 1
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses