Skip to main content
Menu
CVEs

CVE

Difuse authentication bypass in viewToken cookie handling

CVE-2026-129547EUVD-2026-126287GHSA-RGG7-8C9P-JRJJ

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

8.7HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Do first: Workaround: 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.

Published
Last modified
Reference
Last checked
44/100 · provisional
Unclear
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: yes
  • Technical impact: partial

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.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original 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.

Who should check

Teams running Kalmia 0.2.0 or earlier with RequireAuth documentation sites

“Affecting Kalmia <= 0.2.0”

vulncheck.com

cve.now Index

44Pcve.now Index 44 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach10/20Affects Go packages
  • Severity8.7/10CVSS 8.7
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 89 if added to CISA KEV
  • Would score about 84 if CISA's SSVC rates exploitation active
  • Would score about 49 if advisories confirm default setups are exposed

What to do

  • Workaround: 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.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

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"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

Evidence 6

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 4

  1. Report
  2. Repository
  3. Repository
  4. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129547

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: cve.now feed data

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: vulncheck.com

Which versions are affected by CVE-2026-129547?

git.difuse.io/Difuse/kalmia (Go): through 0.2.0.Source: cve.now feed data

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: vulncheck.com

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: vulncheck.com

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: vulncheck.com