# CVE-2026-129139: paicoding commit b8206b9 through 903adce Predictable ZSXQ Account Credentials


- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-vr22-hjrf-w5jq

## What is CVE-2026-129139?

CVE-2026-129139 is a high-severity vulnerability in itwanger paicoding, published on 13 Nov 2026. 

### Official description

paicoding from commit b8206b9 through commit 903adce uses predictable credentials for accounts created via ZSXQ login, because loginByZsxq derives both the username and password solely from the member's ZSXQ number. Unauthenticated attackers can read that number from the victim's /user/{userId} profile page, compute the credentials, and log in via /login/username to take over the account.

Weakness: CWE-1391 (Use of Weak Credentials)

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


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

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

## Is CVE-2026-129139 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-129139 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-129139 is a high-severity vulnerability in itwanger paicoding, published on 13 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-129139 exists.

Affected product: itwanger paicoding. 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-129139/ (Markdown: https://insights.sbomify.com/CVE-2026-129139/index.md)
```

## Sources

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

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