Skip to main content
Menu
CVEs

CVE

Difuse information disclosure in documentation API

Only affects Kalmia through 0.2.0 where documentation records have Git deployment credentials (GitUser, GitPassword) stored. No fixed version is named in the checked facts.

CVE-2026-129546EUVD-2026-126288GHSA-WH29-6MMX-3PR2

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

7.1HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Documentation records have Git deployment credentials (GitUser, GitPassword) stored

Published
Last modified
Reference
Last checked
30/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

Kalmia, a product from DifuseHQ, through version 0.2.0 has an information disclosure flaw that lets a logged-in read-only user retrieve plaintext Git deployment credentials through its documentation API. An attacker can reach it remotely over the network with low-privilege login, and can then use those credentials to access external Git repositories.

Original description

Kalmia through 0.2.0 contains an information disclosure vulnerability that allows authenticated read-only users to retrieve Git deployment credentials via documentation API responses. Attackers can query GET /kal-api/docs/documentations or POST /kal-api/docs/documentation to obtain plaintext gitUser and gitPassword values and authenticate to external Git repositories.

Who should check

Teams running DifuseHQ Kalmia (Go) 0.2.0 or earlier that store Git deployment credentials in documentation settings.

“Affecting Kalmia <= 0.2.0”

vulncheck.com

cve.now Index

30Pcve.now Index 30 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects Go packages
  • Severity7.1/10CVSS 7.1
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 80 if added to CISA KEV
  • Would score about 75 if CISA's SSVC rates exploitation active
  • Would score about 37 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Documentation records have Git deployment credentials (GitUser, GitPassword) stored
  • Workaround: The checked facts name no workaround. The exposure depends on GitUser and GitPassword being stored in documentation records, so that is the setting to review while no fix is available.

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-129546 (Kalmia through 0.2.0 Git Credential Disclosure via Documentation API), 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-129546 (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):
- Documentation records have Git deployment credentials (GitUser, GitPassword) stored (source: https://www.vulncheck.com/advisories/kalmia-through-0.2.0-git-credential-disclosure-via-documentation-api)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-129546 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129546 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/services/docs_docs.go#L52-L55
- https://github.com/DifuseHQ/Kalmia
- https://www.vulncheck.com/advisories/kalmia-through-0.2.0-git-credential-disclosure-via-documentation-api
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-129546
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-129546"}.

Timeline

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

    Exploitation: none · Automatable: no · 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-129546

Is CVE-2026-129546 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?

Documentation API responses can expose Git deployment credentials, including plaintext Git usernames and passwords. An attacker who reads them can use them to authenticate to external Git repositories.Source: vulncheck.com

Which versions are affected by CVE-2026-129546?

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 0.2.0 is affected where documentation records have GitUser and GitPassword stored. To check a setup, look at whether documentation records include those Git deployment fields.Source: vulncheck.com

How do I fix CVE-2026-129546?

The checked facts do not name a fixed version or vendor patch identifiers, so no upgrade target can be given. Check the vendor's project for an update that addresses this issue.Source: vulncheck.com

What if there's no patch?

The checked facts name no workaround. The exposure depends on GitUser and GitPassword being stored in documentation records, so that is the setting to review while no fix is available.Source: vulncheck.com