# CVE-2026-129493: Bolo (bolo-solo) 1.7 through 2.6.4 Article Password Disclosure via /articles

> Unauthenticated attackers can read plaintext article view passwords from Bolo's articles endpoint and access password-protected articles.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/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
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 16 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-j548-r5c7-vvjh

## What is CVE-2026-129493?

CVE-2026-129493 is a high-severity information disclosure vulnerability in bolo-blog bolo-solo, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Bolo (bolo-solo) 1.7 through 2.6.4 contains an information disclosure vulnerability that allows unauthenticated attackers to read article view passwords via the public GET /articles endpoint. Attackers can retrieve the plaintext articleViewPwd field returned by ArticleProcessor.getArticlesByPage and submit it to read password-protected article content.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

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

1 open source package ship an affected version, including bolo-blog/bolo-solo.

An affected version is exposed as installed. No special setting or call is needed.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `bolo-blog/bolo-solo` | GitHub | `pkg:github/bolo-blog/bolo-solo` | From 1.7 to 2.6.4 | None |

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

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

## Is CVE-2026-129493 being exploited?

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

Public exploit code:

- bolo-solo 1.7-2.6.4: GET /articles ships the plaintext articleViewPwd of protected articles to any anonymous visitor (paginated path skips removeUnusedProperties); leaked pwd unlocks the content via /console/article-pwd. Real v2.6.4 build; synthetic fixed side. (github_poc): https://github.com/googlesky/CVE-2026-129493

## Fix prompt for AI coding agents

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

What it is: CVE-2026-129493 is a high-severity information disclosure vulnerability in bolo-blog bolo-solo, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-129493 exists.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected packages and fixed versions:
- bolo-blog/bolo-solo (GitHub): affected from 1.7 up to 2.6.4; no fix listed

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-129493/ (Markdown: https://insights.sbomify.com/CVE-2026-129493/index.md)
```

## Sources

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

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