# CVE-2026-9139: Taiko AG1000-01A Rev 7.3/8 Hard-coded Credentials via login.zhtml

> Hard-coded credentials in client-side JavaScript allow unauthenticated attackers to gain full administrative access to the Taiko SMS Alert Gateway.

- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 May 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-jj2w-phrm-32r8

## What is CVE-2026-9139?

CVE-2026-9139 is a critical vulnerability in Taiko Network Communications Pte Ltd. AG1000-01A SMS Alert Gateway, published on 20 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Taiko AG1000-01A SMS Alert Gateway Rev 7.3 and Rev 8 contains a hard-coded credential vulnerability in the embedded web configuration interface where authentication is implemented entirely in client-side JavaScript in login.zhtml, exposing static plaintext credentials in the page source. Unauthenticated attackers with network access can recover administrative credentials directly from the client-side validate() function to obtain full administrative access to the device.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2026-9139?


## How do I fix CVE-2026-9139?

No fix has been published for CVE-2026-9139 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-9139 being exploited?

There is no known exploitation of CVE-2026-9139 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9139 and fix it if it is affected.

What it is: CVE-2026-9139 is a critical vulnerability in Taiko Network Communications Pte Ltd. AG1000-01A SMS Alert Gateway, published on 20 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9139 in the wild and no public exploit code.

Affected product: Taiko Network Communications Pte Ltd. AG1000-01A SMS Alert Gateway. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9139/ (Markdown: https://insights.sbomify.com/CVE-2026-9139/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9139
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9139
- OSV: https://osv.dev/vulnerability/CVE-2026-9139

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9139/
Summaries are generated and may contain mistakes; the official description above is the record.