Preliminary research

eMudhra CA Key Compromise: Response Guide for Developers

SafeDep Team · SafeDep · 22 October 2026

AI-collected research leads through 3 November 2026, including a November–October–September missed-article review and a targeted multilingual search alongside earlier community-source sweeps. Unranked, incomplete, not community-vetted, and subject to change.

Test both cross-signed trust paths and separate browser blocklists from OS bundles, compiled runtime roots, package bundles and actual application proxy behavior. Positive, negative and inconclusive controls avoid equating failed connectivity with rejection.

Record

Researcher

SafeDep Team

Published by

SafeDep

Date

22 October 2026

In the archive

• Collected in the 2026 preliminary research sweep

Related sources

• Earlier technical explanation
• Chrome and Android response

Tags

• tls
• pki
• certificate-validation
• trust-boundary
• ci-cd
• owasp-a02-2021
• owasp-a08-2021

This page is the archive's own catalogue record. The research is the work of SafeDep Team, first published at the original source. Preserved copies are kept so the citation survives its host.