The irony hit on a Friday afternoon.

New research shows how Git services can implement efficient end-to-end encryption without sacrificing performance or compatibility.

July Patch Tuesday also introduces the next phase in the security hardening rollout for Kerberos on Windows domain controllers.

Don't waste hours scrubbing history while a live key is still active. Rotate first, clean second, and automate your protection for the future.

At a glance Organization Multiple organizations worldwide Data Exposed AWS keys, Stripe secrets, GitHub tokens, internal records Affected Count 28,000 repositories across 3.5 million hosts Cause Publicly exposed .git directory misconfiguration Disclosure Status Public security research report Source Intruder Research Security researchers discovered over 28,000 exposed Git repositories across 3.5 million active web servers. These misconfigured repositories exposed live AWS keys, Stripe payment secrets, and private internal records.

Today, the Git project released new versions to address seven security vulnerabilities that affect all prior versions of Git.

AI coding models frequently insert hardcoded credentials into generated code because they learned "working" patterns from public repositories, which puts secrets into source files, git history, and client-side bundles. Prevent with a fast pre-commit scanner and deep-history verification—Gitleaks blocks commits while TruffleHog scans history and verifies live credentials to prioritize rotation. #Gitleaks #TruffleHog

The vulnerability CVE-2026-30832 affects charmbracelet's soft-serve, a self-hosted Git server designed for command-line use. Versions from 0.6.0 to before 0.11.4 contain a Server-Side Request Forgery (SSRF) flaw categorized under CWE-918. A

Explore Clone2Leak vulnerabilities in Git, exposing credential flaws and posing threats to software security environments.