Skip to main content
VulnerabilityPublished Updated

CVE-2025-68131: Keeper commander · CBORDecoder reuse can leak shareable values across decode calls

Affects keeper-commanderSource GCVE Database

0
Compare
Authoritative record:CVE-2025-68131· Medium 5.5

Public exploit available · CVSS 5.5 Medium : upgrade to 17.2.1_1 or 17.1.13 as a priority.

Data as of 5 Nov 2026, 19:51 UTC

CVSS 4.0 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 17.2.1_1, 17.1.13
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade keeper-commander to 17.2.1_1 or 17.1.13.

Affected software

ProductAffectedFixed in
Homebrewkeeper-commanderpkg:brew/keeper-commanderOther threatsAffected
  • >=17.1.12 <17.1.13
  • >=17.1.14 <17.2.1_1
Fixed in
  • 17.1.13
  • 17.2.1_1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in keeper-commander versions 17.1.13 and 17.2.1_1 that resets the shareables list appropriately between decode operations. Users should upgrade to these fixed versions to remediate the vulnerability. No additional mitigation is required once patched. If upgrading is not immediately possible, avoid reusing CBORDecoder instances across trust boundaries to prevent information leakage.

Description

A vulnerability in keeper-commander's CBORDecoder allows information disclosure when the decoder instance is reused across multiple decode operations. Values tagged as shareable (tag 28) persist in memory and can be accessed by subsequent messages using the sharedref tag (29), enabling an attacker-controlled message to read data from previously decoded messages. This occurs because the shareables list is not cleared between decode calls. The issue affects both the C extension and pure Python implementations. Fixed versions are 17.1.13 and 17.2.1_1.

References

Community reviews

Loading reviews…