CVE
Difuse privilege escalation in Kalmia's user edit endpoint
Affects Kalmia through 0.2.0. The checked facts give no vendor rating and no fixed version.
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:H/VA:H/SC:N/SI:N/SA:N
- 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. Kalmia through 0.2.0 (affecting Kalmia <= 0.2.0)
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 32/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Kalmia, from DifuseHQ, has a privilege escalation flaw in its /kal-api/auth/user/edit endpoint. A remote attacker with a low-privileged, read-only login can modify any account, granting themselves admin rights or resetting an administrator's password to take full control of the instance.
Original description
Kalmia through 0.2.0 contains a privilege escalation vulnerability that allows low-privileged authenticated users to modify any account via the /kal-api/auth/user/edit endpoint. Attackers holding only read permission can set their admin flag and 'all' permission or reset an administrator's password to fully take over the instance.
Who should check
Anyone running DifuseHQ Kalmia (Go) through version 0.2.0, including the current main branch.
“Affecting Kalmia <= 0.2.0”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects Go packages
- Severity8.7/10CVSS 8.7
- No patch5/5No patch listed yet
What would change the score
- Would score about 82 if added to CISA KEV
- Would score about 77 if CISA's SSVC rates exploitation active
- Would score about 39 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Kalmia through 0.2.0 (affecting Kalmia <= 0.2.0)Workaround: The checked facts contain no workaround or mitigation. They do not say how to limit exposure 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-129545 (Kalmia through 0.2.0 Privilege Escalation via /kal-api/auth/user/edit), 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-129545 (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 0.2.0 (affecting Kalmia <= 0.2.0) (source: https://www.vulncheck.com/advisories/kalmia-through-0.2.0-privilege-escalation-via-kal-api-auth-user-edit)
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-129545 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129545 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/auth.go#L183-L232
- https://github.com/DifuseHQ/Kalmia
- https://www.vulncheck.com/advisories/kalmia-through-0.2.0-privilege-escalation-via-kal-api-auth-user-edit
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-129545
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-129545"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
through 0.2.0
Evidence 6
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129545
Is CVE-2026-129545 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?
A user with only read permission can modify any account through the /kal-api/auth/user/edit endpoint. This includes setting their own admin flag and 'all' permission or resetting an administrator's password, which allows full takeover of the instance.Source: vulncheck.com
Which versions are affected by CVE-2026-129545?
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. To check an installation, compare the installed Kalmia version against 0.2.0 or earlier.Source: vulncheck.com
How do I fix CVE-2026-129545?
The checked facts name no fixed version and no vendor patch ids, so no upgrade target can be stated from them.Source: vulncheck.com
What if there's no patch?
The checked facts contain no workaround or mitigation. They do not say how to limit exposure while no fix is available.Source: vulncheck.com