CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

Cisco ThousandEyes Enterprise Agent

product · product:cisco-thousandeyes-enterprise-agent

Coverage
1
first 2026-10-21 → last 2026-10-25
Latest activity
2026-10-25
Eight eMudhra CA keys were guessable; Java needs a second update, and Python, Go, Rust and curl stacks need…
Peak priority
notable
1 notable
Targets
·
no sector or region stated
Sources cited
17
14 hosts

Action items (3)

Do-now tasks recorded on the entries about Cisco ThousandEyes Enterprise Agent, newest first. Check the date before acting on an older one.

  • Update every non-browser TLS client that keeps its own CA bundle or does not check revocation, starting with standalone Java runtimes, including those already updated on 2026-10-21 (Oracle's Security Alert CVE-2026-114820 or the OpenJDK update), pip 26.2.2 or later in every Python environment, Go 1.27.3 or 1.26.10, and the CA bundles and base images the incident tracker lists, rebuild container images that embed an older bundle, then confirm with curl against the tracker's test host that the client rejects the certificate.
    2026-10-21CVE-2026-91403 +2
  • Replace before 2026-10-27 every TLS certificate your organisation holds that chains to emSign ECC Root CA - G3, by hand where the ACME client does not support ACME Renewal Information, because standard ACME clients do not replace a certificate outside its renewal window.
    2026-10-21CVE-2026-91403 +2
  • Apply Cisco's remediation for the products its eMudhra advisory lists as impacted: a TLS policy on Secure Firewall Management Center that blocks the known eMudhra issuers, Duo Access Gateway 3.2.0, Duo Network Gateway 3.4.1, Duo Agentic Authorization Connector 1.0.1 and ThousandEyes Enterprise Agent (Application-hosting Agent 5.2.2) now, and Meraki MV Smart Camera Firmware (2026-11-18), IOS XR 26.4.1 (2026-11-30) and Ultra Cloud Core Subscriber Microservices Infrastructure 2026.04.1 (November 2026) when they ship; other Cisco products are still under investigation.
    2026-10-21CVE-2026-91403 +2

Defender insights

What each entry about Cisco ThousandEyes Enterprise Agent tells a defender to do, newest first.

2026-10-21NOTABLEEight eMudhra CA keys were guessable; Java needs a second update, and Python, Go, Rust and curl stacks need theirs

Exposure · triage · detection

Story timeline

  1. 2026-10-21eMudhra: the private keys of eight intermediate CA certificates were trivially recoverable, so anyone could forge trusted HTTPS certificates; browsers block them, clients with their own trust store or no revocation checking need an update (CVE-2026-111943 in Go)
    active-threatsEight eMudhra CA keys were guessable; Java needs a second update, and Python, Go, Rust and curl stacks need theirs

Hunting pivots

CVEs
CVE-2026-114820CVE-2026-115557CVE-2026-91403
Releases covered
Cisco ThousandEyes Enterprise Agent
Tags
patch-availablesupply-chain
ATT&CK techniques (1 across 2 tactics)

1 technique observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.0 · compare on the matrix · Navigator layer (JSON)

  • Credential AccessAdversary-in-the-Middle
  • CollectionAdversary-in-the-Middle

Credential Access TA0006

T1557Adversary-in-the-Middle×1

Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as Network Sniffing, Transmitted Data Manipulation, or replay attacks (Exploitation for Credential Access). By abusing features of common networking protocols that can determine the flow of network traffic (e.g. ARP, DNS, LLMNR, etc.), adversaries may force a device to communicate through an adversary controlled system so they can collect information or perform additional actions.

Evidence: 2026-10-21/emudhra-intermediate-ca-keys-recoverable-trust-store-updates · ATT&CK page ↗

Collection TA0009

T1557Adversary-in-the-Middle×1

Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as Network Sniffing, Transmitted Data Manipulation, or replay attacks (Exploitation for Credential Access). By abusing features of common networking protocols that can determine the flow of network traffic (e.g. ARP, DNS, LLMNR, etc.), adversaries may force a device to communicate through an adversary controlled system so they can collect information or perform additional actions.

Evidence: 2026-10-21/emudhra-intermediate-ca-keys-recoverable-trust-store-updates · ATT&CK page ↗

Entries about Cisco ThousandEyes Enterprise Agent (1)

2026-10-21 · view entry permalink →

NOTABLECVE-2026-91403 +2updatedNATOA1

eMudhra: the private keys of eight intermediate CA certificates were trivially recoverable, so anyone could forge trusted HTTPS certificates; browsers block them, clients with their own trust store or no revocation checking need an update (CVE-2026-111943 in Go)

On 2026-10-17 a researcher reported to the Chrome Root Program, and Mozilla received a report the same day, that the private keys of eight eMudhra subordinate CA certificates were compromised: the keys were generated with insufficient randomness, which lets anyone forge trusted HTTPS certificates to impersonate any website against clients that have not removed trust in those CAs (Google, 2026-10-20; Mozilla, 2026-10-20). BleepingComputer, citing Mozilla's incident report, says all eight were P-384 keys generated in April 2025 with values below 256, so testing 256 numbers recovers a key, and that eMudhra blames a key-generation script error and found no evidence of end-user certificates (BleepingComputer, 2026-10-20). Google reports that no certificates chaining to the six TLS intermediates were logged to Certificate Transparency before it blocked them, so CT-enforcing clients such as Chrome could not have been attacked (Google, 2026-10-20); the tracker adds that many clients outside browsers do not enforce CT and that it is not known whether attackers used the flaw against them (Dennis Jackson, 2026-10-20).

Chrome blocked the intermediates on 2026-10-17, Firefox through OneCRL the same day, Microsoft platforms on 2026-10-20 and Apple devices on 2026-10-22, and eMudhra revoked all eight (Dennis Jackson, 2026-10-20; BleepingComputer, 2026-10-20). Google removed the root that signed them, emSign ECC Root CA - G3, from the Chrome Root Store, with the removal expected to reach devices on 2026-10-27, after which some legitimate certificates chaining to it will stop working in Chrome (Google, 2026-10-20); Mozilla removes the signing root from NSS 3.131.1 to protect applications that use its trust store without OneCRL (Mozilla, 2026-10-20). Go 1.27.3 and 1.26.10 filter chains that contain the intermediates in crypto/x509, tracked as CVE-2026-111943 (Go team, 2026-10-20).

Standalone OpenJDK runtimes, unlike operating-system packages, carry their own keystore (OpenJDK, 2026-10-24). Oracle's Security Alert of 2026-10-21 for CVE-2026-91403 (CVSS 3.1 9.1, component JSSE, remotely exploitable without authentication through the component's APIs, for example a web service that supplies data to them) provided Java updates that distrust the impacted eMudhra intermediate CA certificates (Oracle, 2026-10-21), and a second Security Alert of 2026-10-24, CVE-2026-114820 (CVSS 3.1 9.1, same component and exposure), provides updates that remove the impacted root CA certificates and lists Oracle Java SE 8u511-b32, 11.0.33.0.2, 17.0.21.0.2, 21.0.13.0.2, 25.0.5.0.2 and 27.0.1.0.2 as affected (Oracle, 2026-10-24). The OpenJDK advisory of 2026-10-24 lists 27.0.1.0.2, 25.0.5.0.2, 21.0.13.0.2, 17.0.21.0.2, 11.0.32.1 and 8u504 and earlier as affected (OpenJDK, 2026-10-24), and OpenJDK's guidance tells users of a standalone runtime to act immediately even if they updated in the past few days, preferably by installing an update whose release note names JDK-8395690 and CVE-2026-114820 (OpenJDK, 2026-10-24). If no update is available, OpenJDK gives two alternatives: delete the aliases emsignrootcag1, emsignrootcag2, emsigneccrootcag3 and comodoaaaca from the runtime's cacerts keystore and restart it, or enable revocation checking with -Dcom.sun.net.ssl.checkRevocation=true and -Dcom.sun.security.enableCRLDP=true for TLS clients and use jarsigner -verify -revcheck -strict for signed JARs on JDK 17 and later; the step is repeated for every installed runtime (OpenJDK, 2026-10-24). OpenJDK packages from Arch Linux, Fedora, Gentoo, Oracle Linux and Red Hat Enterprise Linux most likely use the operating system's certificates, so updating those is likely sufficient; Debian and its derivatives, Devuan and Ubuntu among them, need a manual workaround because updating ca-certificates and ca-certificates-java does not refresh the keystore (as superuser, remove /etc/ssl/certs/java/cacerts and run update-ca-certificates --fresh), and the FreeBSD and Homebrew packages need an updated package (OpenJDK, 2026-10-24). NCSC.ch published an advisory on 2026-10-22 and lists the exploitation status as unknown (NCSC.ch, 2026-10-22).

Triage: a site that still chains to emSign ECC Root CA - G3 failing in Chrome after 2026-10-27 is the announced root removal, not an attack (Google, 2026-10-20).

enabling anyone to forge trusted HTTPS certificates to impersonate any website against clients that have not yet removed trust in those CAs.

Google (Chrome Root Program and Android Security) 2026-10-20

many other clients do not consume revocation information and require software updates to ensure they no longer trust the compromised intermediates.

We do not know if attackers exploited the flawed key generation to target these clients.

Dennis Jackson (eMudhra intermediate CA compromise incident tracker) 2026-10-20

crypto/x509: mitigation for security concerns with a specific Certificate Authority

Go team (golang-announce) 2026-10-20

This Security Alert addresses CVE-2026-91403 by providing Java updates which distrusts the set of impacted intermediate CA certificates related to eMudhra.

Oracle (Security Alert CVE-2026-91403) 2026-10-21

This Security Alert addresses CVE-2026-114820 by providing Java updates which removes the set of impacted root CA certificates related to eMudhra.

Oracle (Security Alert CVE-2026-114820) 2026-10-24

take one of the following actions immediately; even if you have updated your runtime in the past few days.

OpenJDK (Compromised Certificates and OpenJDK Java Runtimes) 2026-10-24

Python has added a denylist for known compromised certificates to the "ssl" module to ensure user safety even without certificate revocation configured.

Python Software Foundation (security-announce, CVE-2026-115557) 2026-10-24

Chrome has told eMudhra that standard ACME clients do not replace certificates outside their renewal window unless they support ACME Renewal Information (ARI) or someone steps in by hand.

The Hacker News 2026-10-22
Updaterun 2026-10-23T0256Z-intelheadlinesummaryaffected_productscvessourcesevidenceactionsbodyentities

On 2026-10-21 Oracle issued Security Alert CVE-2026-91403 and the OpenJDK project an advisory for the same event, which reaches Java runtimes as well; Oracle says it also applies to sandboxed Java Web Start and applet clients (Oracle, 2026-10-21). Affected are Oracle Java SE 8u511, 8u511-perf, 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1, GraalVM for JDK 17.0.21 and 21.0.13 and GraalVM Enterprise Edition 21.3.20, and OpenJDK lists 27.0.1, 25.0.5, 21.0.13, 17.0.21, 11.0.32.1 and 8u504 and earlier (Oracle, 2026-10-21; OpenJDK, 2026-10-21). Compare the full build string, not the release number, against Oracle's affected list. NCSC.ch's advisory of 2026-10-22 lists the exploitation status as unknown and the OpenJDK guidance as the temporary mitigation (NCSC.ch, 2026-10-22).

Updaterun 2026-10-25T0256Z-intelheadlinesummarycvesaffected_productsentitiessourcesevidenceactionsbody

Oracle's second Security Alert of 2026-10-24, CVE-2026-114820 (CVSS 3.1 9.1, component JSSE, remotely exploitable without authentication through the component's APIs), provides Java updates that remove the impacted root CA certificates related to eMudhra (Oracle, 2026-10-24). Its affected list names Oracle Java SE 8u511-b32, 11.0.33.0.2, 17.0.21.0.2, 21.0.13.0.2, 25.0.5.0.2 and 27.0.1.0.2, and the OpenJDK advisory of the same day lists 27.0.1.0.2, 25.0.5.0.2, 21.0.13.0.2, 17.0.21.0.2, 11.0.32.1 and 8u504 and earlier as affected (Oracle, 2026-10-24; OpenJDK, 2026-10-24). OpenJDK tells users of a standalone runtime to act immediately even if they updated in the past few days, by installing an update whose release note names JDK-8395690 and CVE-2026-114820 or, failing that, by deleting the cacerts aliases emsignrootcag1, emsignrootcag2, emsigneccrootcag3 and comodoaaaca or enabling revocation checking (OpenJDK, 2026-10-24). The same page now says Debian, Devuan and Ubuntu OpenJDK packages need the keystore recreated by hand, because updating ca-certificates and ca-certificates-java does not refresh it, which replaces the earlier statement that updating the operating system's certificates suffices there (OpenJDK, 2026-10-24).

The Python Software Foundation announced CVE-2026-115557 on 2026-10-24: the ssl module now carries a denylist of known compromised certificates that is rejected whatever the SSLContext policy, so it works without revocation checking (Python Software Foundation, 2026-10-24). ENISA's record scores it 9.4 (CVSS 4.0) and lists CPython before 3.16.0 as affected, and the announcement names no release that carries the denylist (ENISA EUVD, 2026-10-24). The incident tracker lists Python 3.15.1, 3.14.9 and 3.13.17 and pip 26.2.2 as patched, and Christian Heimes stresses in the announcement thread that pip before 26.2.2 keeps trusting the compromised intermediates whatever the system trust store holds, because it always loads its own vendored certifi (Dennis Jackson, 2026-10-20; Python Discourse, 2026-10-20).

Cisco's informational advisory, version 1.1 of 2026-10-24, lists as impacted with remediation a TLS policy that blocks the known eMudhra issuers on Secure Firewall Management Center, Duo Access Gateway 3.2.0, Duo Network Gateway 3.4.1, Duo Agentic Authorization Connector 1.0.1, ThousandEyes Enterprise Agent (Application-hosting Agent 5.2.2, 2026-10-23), Meraki MV Smart Camera Firmware (2026-11-18), IOS XR 26.4.1 (2026-11-30) and Ultra Cloud Core Subscriber Microservices Infrastructure 2026.04.1 (November 2026), keeps further products under investigation, and says Cisco PSIRT is not aware of malicious use (Cisco PSIRT, 2026-10-24).

eMudhra's board decided on 2026-10-22 to leave the global SSL/TLS certificate business, and its G1 RSA roots keep serving customers during the transition (eMudhra, 2026-10-22). The Hacker News relays Chrome's count of about 30,800 unexpired certificates under the emSign ECC Root CA - G3, which Chrome stops trusting on 2026-10-27, as of 2026-10-21, 99.9 percent of them issued through InCommon, and relays Chrome's point that standard ACME clients do not replace a certificate outside its renewal window unless they support ACME Renewal Information or someone steps in by hand (The Hacker News, 2026-10-22).

incident21 Oct 03:43Zmulti-sourceOpen finding →
Sources: Google (Chrome Root Program and Android Security) · Dennis Jackson (eMudhra intermediate CA compromise incident tracker) · Mozilla Security Blog · Go team (golang-announce) · BleepingComputer · Oracle (Security Alert CVE-2026-91403) · OpenJDK (Vulnerability Advisory 2026/10/21) · NCSC.ch Security Hub (advisory 13091) · Oracle (Security Alert CVE-2026-114820) · OpenJDK (Vulnerability Advisory 2026/10/24) · OpenJDK (Compromised Certificates and OpenJDK Java Runtimes) · Python Software Foundation (security-announce, CVE-2026-115557) · ENISA EUVD (EUVD-2026-109299) · Cisco PSIRT (cisco-sa-emudhra-info, version 1.1) · Python Discourse (eMudhra information for Python users) · The Hacker News · eMudhra (press release)

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Threats1

Source distribution

  • openjdk.org3 (18%)
  • oracle.com2 (12%)
  • bleepingcomputer.com1 (6%)
  • blog.google1 (6%)
  • blog.mozilla.org1 (6%)
  • discuss.python.org1 (6%)
  • emudhra.com1 (6%)
  • emudhra.we-have-a-problem.com1 (6%)
  • other6 (35%)
All cited sources (17)