Security readout for executives and security teams
Plain-English summary
Affected Taiko SMS Alert Gateways expose built-in administrator credentials through their web login page. Anyone who can reach that interface may obtain full device control without an existing account or user interaction, threatening message availability, configuration integrity, and information stored or processed by the gateway.
Executive priority
Treat reachable Rev 7.3 or Rev 8 devices as an immediate remediation priority. Rapidly remove public exposure, restrict management access, and obtain vendor direction. Prioritize gateways supporting critical alerting because administrative compromise could disrupt notifications or alter device behavior.
Technical view
The embedded configuration interface performs authentication in client-side JavaScript within login.zhtml. Static plaintext credentials are present in the validate() function, constituting CWE-798. The supplied CVSS 3.1 score is 9.8 because exploitation requires only network access, with no privileges or interaction, and may compromise confidentiality, integrity, and availability.
Likely exposure
Exposure is limited to Taiko AG1000-01A devices whose web configuration interface is reachable by an attacker. Rev 7.3 and Rev 8 are explicitly described as vulnerable. The bundle also lists UM-AG1000_R7.2, but its affected status is unclear and should be verified.
Exploitation context
The source bundle describes low-complexity, unauthenticated network exploitation. It provides no evidence of observed exploitation, and the CVE is not identified as being in KEV. Internet exposure would increase urgency, but internal network access may also be sufficient.
Researcher notes
The bundle consistently identifies client-side authentication and hard-coded credentials, but supplies no vendor patch, workaround, exploitation telemetry, or CPE identifiers. Version data is inconsistent: the narrative names Rev 7.3 and Rev 8, while the affected list also includes UM-AG1000_R7.2. Validate that designation before expanding scope.
Mitigation direction
- Restrict the configuration interface to trusted management networks and authorized administrators.
- Block internet access to the gateway’s web interface.
- Check Taiko guidance for patched firmware or supported remediation; none is identified in the supplied sources.
- Rotate related credentials after remediation and review whether they were reused elsewhere.
- Consider isolating or replacing affected devices if no supported correction is available.
Validation and detection
- Inventory Taiko AG1000-01A gateways and record their exact hardware and firmware revisions.
- Confirm whether each web configuration interface is reachable from internet, user, wireless, or partner networks.
- Inspect authorized configuration artifacts to determine whether login.zhtml contains static plaintext credentials.
- Review device and network logs for unexpected administrative access or configuration changes.
- Verify management-interface restrictions after mitigation from each relevant network segment.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-798: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-9139 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Ledger Security Bulletin 019CVE reference, VulnCheck · technical-description
- https://www.vulncheck.com/advisories/taiko-ag1000-01a-rev-8-hard-coded-credentials-via-login-zhtmlCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Hard-coded Credentials
Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.