CVE-2025-68131: Cbor2 CBORDecoder Reuse Can Leak Shareable Vulnerability

MODERATE
Advisory Identifier: GHSA-wcj4-jw5j-44wh
CWE-212
Published
Advisory Summary

CVE-2025-68131 is a MODERATE cbordecoder reuse can leak shareable vulnerability (CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer) affecting Cbor2 libraries in the PyPI ecosystem. The issue involves cbordecoder reuse can leak shareable values across decode calls. Remediation is available by upgrading affected packages to version 5.8.0.

CVE-2025-68131 at a Glance

CVE Identifier CVE-2025-68131
GHSA Identifier GHSA-wcj4-jw5j-44wh
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer
Affected Product Cbor2
Package Ecosystem PyPI
Published Date
Last Updated

How to Fix CVE-2025-68131

To remediate this vulnerability, upgrade all affected Cbor2 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

cbor2 fixed: 5.8.0
pip install cbor2>=5.8.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show cbor2

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2025-68131, inspect your installed packages using pip:

pip show cbor2

Analyze the terminal output to locate any version of Cbor2 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.8.0), your application is affected.

Note: The pip show cbor2 command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer, where the product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors. In Cbor2, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary When a CBORDecoder instance is reused across multiple decode operations, values marked with the shareable tag (28) persist in memory and can be accessed by subsequent CBOR messages using the sharedref tag (29). This allows an attacker-controlled message to read data from previously decoded messages if the decoder is reused across trust boundaries. ### Details The issue is in the decoder's handling of the shareables list, which stores values tagged with CBOR tag 28 (shareable) for later reference by tag 29 (sharedref). When decode_from_bytes() is called or when .fp is set to a new stream, the shareables list is not cleared. This allows references to persist across separate decode operations. The issue exists in both the C extension and the pure Python decoder. In the C extension (source/decoder.c), the _CBORDecoder_set_fp function (line ~202) updates the file pointer but does not reset the shareables state: ``` static int _CBORDecoder_set_fp(CBORDecoderObject *self, PyObject *value, void *closure) { // ... validation ... tmp = self->read; self->read = read; Py_DECREF(tmp); return 0; // Missing: PyList_Clear(self->shareables) or equivalent } ``` In the pure Python decoder (cbor2/_decoder.py), the fp setter similarly fails to clear self._shareables. Similarly, decode_from_bytes() in both implementations saves and restores the read pointer but does not clear the shareables list between decodes. The shareable/sharedref tags are defined in the CBOR value sharing extension (http://cbor.schmorp.de/value-sharing) with scope limited to a single CBOR data item, not across separate messages. ### PoC ``` import cbor2 from io import BytesIO # Message from trusted source containing a shareable value msg1 = cbor2.dumps(cbor2.CBORTag(28, "secret")) # Attacker-controlled message referencing index 0 msg2 = cbor2.dumps(cbor2.CBORTag(29, 0)) # Decoder reused across trust boundaries decoder = cbor2.CBORDecoder(BytesIO(b'')) decoder.decode_from_bytes(msg1) print(decoder.decode_from_bytes(msg2)) # prints "secret" ``` No special configuration required. Affects any application that reuses a CBORDecoder instance to decode messages from different sources. ### Impact Information disclosure. Applications that reuse a CBORDecoder across trust boundaries are vulnerable if the trusted messages use value sharing (tag 28) and an attacker can send messages containing shared references (tag 29). An attacker who can send a crafted CBOR message containing a sharedref tag can read values from previously decoded messages, potentially exposing sensitive data such as credentials, tokens, or private user data. ### Related A similar issue in the encoder could produce invalid CBOR with dangling shared references: ``` import cbor2 from io import BytesIO # Create encoder with value sharing enabled encoder = cbor2.CBOREncoder(BytesIO(), value_sharing=True) # Persistent object that will be encoded multiple times shared_obj = ['hello'] # First encode: array containing shared_obj twice encoder.encode([shared_obj, shared_obj]) print(f'First encode: {encoder.fp.getvalue().hex()}') # Output: d81c82d81c816568656c6c6fd81d01 # Second encode: just shared_obj encoder.fp = BytesIO() encoder.encode(shared_obj) result = encoder.fp.getvalue() print(f'Second encode: {result.hex()}') # Output: d81d01 (just a shared reference to index 1!) # Try to decode the second result as standalone CBOR decoder = cbor2.CBORDecoder(BytesIO(result)) decoded = decoder.decode() # FAILS: shared reference 1 not found ``` While primarily a correctness bug, it could cause denial of service if invalid CBOR is transmitted to downstream systems that fail to parse it, or cause silent data corruption if the dangling reference happens to resolve to an unrelated value. It can also be considered a memory leak in both the decoder and encoder as references are held that will never be released as long as the decoder/encoder remains alive. ### Suggested resolution Add dedicated boolean flags to track when an encode/decode operation is in progress. Reset shared state only when the flag is False (top-level call). This ensures state is reset for standalone calls while preserving shared references for nested calls from hooks (which need access to the registry for cyclic structures). Decoder (_decoding flag): - decode(): set flag True, reset state, decode, set flag False - decode_from_bytes(): reset state only when flag is False Encoder (_encoding flag): - encode(): set flag True, reset state, encode, set flag False - encode_to_bytes(): reset state only when flag is False

CVE-2025-68131 Affected Cbor2 Versions

1 component(s)
Fixed Versions:
5.8.0
Product / Package Ecosystem Affected Versions Fixed Version
cbor2
PyPI
≥ 3.0.0
< 5.8.0
5.8.0

References

Frequently Asked Questions

What is CVE-2025-68131?
CVE-2025-68131 is a security vulnerability in Cbor2 involving CBORDecoder reuse can leak shareable values across decode calls under CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer.
Which Cbor2 versions are affected?
Affected versions include releases prior to 5.8.0 across affected packages: cbor2.
What version fixes CVE-2025-68131?
Upgrading to 5.8.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is cbor2 affected?
Yes, cbor2 is affected in releases prior to 5.8.0. Upgrade your dependency to 5.8.0 or later.
What CWE is associated with CVE-2025-68131?
CVE-2025-68131 is classified under CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer (The product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors.).
How can I check PyPI dependencies for CVE-2025-68131?
Run the dependency tree command: 'pip show cbor2'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-wcj4-jw5j-44wh",
  "modified" : "2026-06-05T14:17:47Z",
  "published" : "2025-12-31T22:01:38Z",
  "aliases" : [ "CVE-2025-68131" ],
  "summary" : "CBORDecoder reuse can leak shareable values across decode calls",
  "details" : "### Summary\nWhen a CBORDecoder instance is reused across multiple decode operations, values marked with the shareable tag (28) persist in memory and can be accessed by subsequent CBOR messages using the sharedref tag (29). This allows an attacker-controlled message to read data from previously decoded messages if the decoder is reused across trust boundaries.\n\n### Details\nThe issue is in the decoder's handling of the shareables list, which stores values tagged with CBOR tag 28 (shareable) for later reference by tag 29 (sharedref).\n\nWhen decode_from_bytes() is called or when .fp is set to a new stream, the shareables list is not cleared. This allows references to persist across separate decode operations.\n\nThe issue exists in both the C extension and the pure Python decoder.\n\nIn the C extension (source/decoder.c), the _CBORDecoder_set_fp function (line ~202) updates the file pointer but does not reset the shareables state:\n\n```\n  static int\n  _CBORDecoder_set_fp(CBORDecoderObject *self, PyObject *value, void *closure)\n  {\n      // ... validation ...\n      tmp = self->read;\n      self->read = read;\n      Py_DECREF(tmp);\n      return 0;\n      // Missing: PyList_Clear(self->shareables) or equivalent\n  }\n```\n\nIn the pure Python decoder (cbor2/_decoder.py), the fp setter similarly fails to clear self._shareables.\n\nSimilarly, decode_from_bytes() in both implementations saves and restores the read pointer but does not clear the shareables list between decodes.\n\nThe shareable/sharedref tags are defined in the CBOR value sharing extension (http://cbor.schmorp.de/value-sharing) with scope limited to a single CBOR data item, not across separate messages.\n\n### PoC\n\n```\nimport cbor2\nfrom io import BytesIO\n\n# Message from trusted source containing a shareable value\nmsg1 = cbor2.dumps(cbor2.CBORTag(28, \"secret\"))\n\n# Attacker-controlled message referencing index 0\nmsg2 = cbor2.dumps(cbor2.CBORTag(29, 0))\n\n# Decoder reused across trust boundaries\ndecoder = cbor2.CBORDecoder(BytesIO(b''))\ndecoder.decode_from_bytes(msg1)\nprint(decoder.decode_from_bytes(msg2))  # prints \"secret\"\n```\nNo special configuration required. Affects any application that reuses a CBORDecoder instance to decode messages from different sources.\n\n### Impact\nInformation disclosure. Applications that reuse a CBORDecoder across trust boundaries are vulnerable if the trusted messages use value sharing (tag 28) and an attacker can send messages containing shared references (tag 29). An attacker who can send a crafted CBOR message containing a sharedref tag can read values from previously decoded messages, potentially exposing sensitive data such as credentials, tokens, or private user data.\n\n### Related\nA similar issue in the encoder could produce invalid CBOR with dangling shared references:\n\n```\nimport cbor2\nfrom io import BytesIO\n\n# Create encoder with value sharing enabled\nencoder = cbor2.CBOREncoder(BytesIO(), value_sharing=True)\n\n# Persistent object that will be encoded multiple times\nshared_obj = ['hello']\n\n# First encode: array containing shared_obj twice\nencoder.encode([shared_obj, shared_obj])\nprint(f'First encode: {encoder.fp.getvalue().hex()}')\n# Output: d81c82d81c816568656c6c6fd81d01\n\n# Second encode: just shared_obj\nencoder.fp = BytesIO()\nencoder.encode(shared_obj)\nresult = encoder.fp.getvalue()\nprint(f'Second encode: {result.hex()}')\n# Output: d81d01  (just a shared reference to index 1!)\n\n# Try to decode the second result as standalone CBOR\ndecoder = cbor2.CBORDecoder(BytesIO(result))\ndecoded = decoder.decode()\n# FAILS: shared reference 1 not found\n```\n\nWhile primarily a correctness bug, it could cause denial of service if invalid CBOR is transmitted to downstream systems that fail to parse it, or cause silent data corruption if the dangling reference happens to resolve to an unrelated value.\n\nIt can also be considered a memory leak in both the decoder and encoder as references are held that will never be released as long as the decoder/encoder remains alive.\n\n### Suggested resolution\n\nAdd dedicated boolean flags to track when an encode/decode operation is in progress. Reset shared state only when the flag is False (top-level call). This ensures state is reset for standalone calls while preserving shared references for nested calls from hooks (which need access to the registry for cyclic structures).\n\nDecoder (_decoding flag):\n - decode(): set flag True, reset state, decode, set flag False\n - decode_from_bytes(): reset state only when flag is False\n\nEncoder (_encoding flag):\n - encode(): set flag True, reset state, encode, set flag False\n - encode_to_bytes(): reset state only when flag is False",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "cbor2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.0.0"
      }, {
        "fixed" : "5.8.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/agronholm/cbor2/security/advisories/GHSA-wcj4-jw5j-44wh"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-68131"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/agronholm/cbor2/pull/268"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/agronholm/cbor2/commit/f1d701cd2c411ee40bb1fe383afe7f365f35abf0"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/agronholm/cbor2"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pypa/advisory-database/tree/main/vulns/cbor2/PYSEC-2025-90.yaml"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-212" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-12-31T22:01:38Z",
    "nvd_published_at" : "2025-12-31T02:15:42Z"
  }
}