eMudhra emBridge flaw: CERT-In flags LAN file name listing
CERT-In rates a flaw in eMudhra emBridge low severity: a LAN attacker could list file names; upgrade to the fixed emBridge versions.
- Published
- Updated
- Ecosystem
- Desktops, browsers and mobile
- Fixed in
- Windows 5.9.4.x or later, macOS (x64) 3.2.7.x or later, Ubuntu (x64) 3.3.1.x or later, Red Hat (x64) 3.3.1.x or later
- Exploitation
- No exploitation reported in the sources; not confirmed either way
What happened
CERT-In issued vulnerability note CIVN-2026-0549 on November 13, 2026, titled “Information Disclosure Vulnerability in eMudhra emBridge”, with a LOW severity rating CERT-In.
emBridge is a client-side utility that lets web applications work with digital signature certificates and hardware tokens. According to CERT-In, the FileBrowser API endpoints lack authorization checks and enumerate the file system using the LocalSystem account without validating the caller. An unauthenticated attacker on the same LAN could send a malicious webpage to the local HTTPS Web API and learn file and directory names and the directory structure CERT-In.
CERT-In states the flaw does not give access to file contents, file modification or deletion, code execution, cryptographic keys or hardware token PINs. The flaw was reported by Karan Saini CERT-In.
Inc42 and Medianama both report that eMudhra says it fixed the issue on November 11, two days before the CERT-In note, by removing the file-browsing functions from emBridge. Both also report eMudhra’s view that an attack needs several conditions at once: an affected version, a malicious webpage on the same local network, the user opening it, and a browser without Local Network Access restrictions. eMudhra also says its firewall and local-only request handling block direct access from other machines Inc42, Medianama.
Severity is mildly disputed. Inc42 and Medianama report that Saini called the bug trivial and said eMudhra’s own advisory downplays it, while eMudhra rates impact and risk as low Inc42, Medianama.
Context: Inc42 and Medianama both link the story to eMudhra’s October incident, in which a researcher reported on October 17 that private keys behind eight intermediate CA certificates were weak. Inc42 states the emBridge bug sits in the domestic signing stack, which the government had said was untouched by that incident. Medianama attributes that point to Inc42. The CERT-In note does not mention the October incident Inc42, Medianama.
Am I affected?
CERT-In lists these affected versions CERT-In:
| Platform | Affected | Upgrade to |
|---|---|---|
| Windows | 5.9.1.x to 5.9.3.x | 5.9.4.x or later |
| macOS (x64) | 3.2.4.x to 3.2.6.x | 3.2.7.x or later |
| Ubuntu (x64) | 3.2.0.x to 3.3.0.x | 3.3.1.x or later |
| Red Hat (x64) | 3.2.0.x to 3.3.0.x | 3.3.1.x or later |
CERT-In’s target audience is all organizations and individuals using affected versions. Inc42 reports that government portals such as the MCA V3 portal, DGFT and the National Single Window System rely on emBridge for DSC-based signing, and that the Income Tax Department recommends it for managing DSCs Inc42.
Exploitation in the wild is not reported in the sources and is not confirmed.
What to do now
- Check the installed emBridge version on each machine and compare it with the table above.
- Upgrade to the fixed version for your platform: 5.9.4.x or later on Windows, 3.2.7.x or later on macOS, 3.3.1.x or later on Ubuntu and Red Hat CERT-In.
- For vendor details, see eMudhra’s own advisory, which CERT-In lists as its vendor reference. The sources do not give further vendor guidance.
- Treat the impact as limited to file and directory names, as CERT-In describes. No key or token PIN exposure is reported, so the sources give no reason to rotate keys or PINs.