Join our Newsletter — 33% off our NHI Course

Who is exposed when 2,622 valid certificates stay live?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20230
Topic starter  

TL;DR: GitGuardian's data set links more than 40,000 leaked private keys to 140,000 TLS certificates and finds 2,622 still valid as of September 2025. Certificate revocation has to outpace disclosure, or exposed trust material can keep working long after discovery.

Editorial analysis by NHI Mgmt Group, based on content published by GitGuardian: “2,622 Valid Certificates Exposed: A Google-GitGuardian Study Maps Private Key Leaks to Real-World Risk”.

By the numbers:

  • Since 2021, GitGuardian detected about one million unique private keys leaked across GitHub and DockerHub.
  • As of September 2025, 2,600 of the mapped certificates were still valid.
  • GitGuardian sent 4,300 disclosure emails to 600 organizations, but only 54 responded.

Key questions

Q: Why do leaked certificate keys remain risky after disclosure?

A: They remain risky because ownership is often unclear, revocation is slow, and replacement certificates do not automatically invalidate the original key.

Q: How should teams measure whether certificate revocation is actually working?

A: Teams should measure the time from exposure detection to confirmed revocation, the percentage of leaked keys mapped to owners, and the share of certificates that remain valid after disclosure.

Q: What breaks when a leaked private key is still tied to a valid certificate?

A: The trust model breaks because the exposed key can continue to authenticate a website or service even after the leak is known.

Practitioner guidance

Bottom line: Leaked private keys create a trust problem that extends well beyond secret detection, because the same key can continue to validate live certificates.

Glossary terms: Private Key Exfiltration, Certificate Transparency, Cryptoperiod, Certificate Revocation List

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 7 days ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20712
 

Private key leakage is a certificate governance failure, not a detection problem. The article shows that finding exposed keys is often easier than proving what they still control. That shifts the real control point to ownership attribution, certificate linkage, and revocation execution. For identity programmes, the lesson is that discovery without lifecycle closure leaves trust material live.

A few things that frame the scale:

A question worth separating out:

Q: Should organisations rotate private keys before or after certificate renewal?

A: They should rotate keys before renewal whenever possible, and they should not rely on renewal to clean up exposure. If the old key remains valid, renewal only adds another certificate to the estate while leaving the compromised trust material in place.

👉 Read our full editorial: Private key leaks expose certificate governance gaps at internet scale



   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.