Vulnerabilities in pkg:pypi/graphitedb

PACKAGE
Share
Advisory Summary

GHSA-qw48-84f6-28gv is a HIGH (CVSS 7.8) graphite has a pickle deserialization vulnerability (CWE-502: Deserialization of Untrusted Data) affecting Graphitedb libraries in the PyPI ecosystem. The issue involves graphite has a pickle deserialization vulnerability. Remediation is available by upgrading affected packages to version 0.2.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:pypi/graphitedb

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:pypi/graphitedb. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-qw48-84f6-28gv - HIGH Graphite Has a Pickle Deserialization Vulnerability

GHSA-qw48-84f6-28gv at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-qw48-84f6-28gv
Severity HIGH
CVSS v3.1 Base Score 7.8
CWE Classification CWE-502: Deserialization of Untrusted Data
Affected Product Graphitedb
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 7.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix GHSA-qw48-84f6-28gv

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

graphitedb fixed: 0.2 
pip install graphitedb>=0.2
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 graphitedb

How to Check if You Are Affected

To determine whether your Python environment is affected by GHSA-qw48-84f6-28gv, inspect your installed packages using pip:

pip show graphitedb

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

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

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-502: Deserialization of Untrusted Data, where the product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. In Graphitedb, 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

### Impact **Type of vulnerability:** Insecure Deserialization via Python's `pickle` module. **Who is impacted:** Users of *Graphite graph database engine* versions **before 0.2** who load database files from untrusted or third-party sources. An attacker could craft a malicious database file that executes arbitrary code when loaded by the engine. This is possible because the engine used `pickle` for serialization, which is known to be unsafe for untrusted data. ### Patches The vulnerability has been patched starting from **version 0.2**. All users should upgrade to **version 0.2 or later** (the current version is 0.4 at publishing time). In version 0.2 and above, the engine uses **JSON** instead of `pickle` for database storage, eliminating the deserialization risk. ### Workarounds If users cannot upgrade immediately: 1. **Do not load database files from untrusted or unknown sources** when using versions <0.2. 2. **Migrate existing pickle-based databases** to the new JSON format using the provided migration module: ```python from graphite.Migration import convert_pickle_to_json convert_pickle_to_json("path/to/old_database.pkl", "path/to/new_database.json") ``` After migration, you can safely use the database with version 0.2+. **Note:** Versions 0.2 and later will show a **warning** when attempting to load legacy pickle files, reminding you to migrate them. Also, **you can't load pickle files** in 0.2 and later. ### Resources - Upgrade to [v0.2 or newer](https://github.com/mkh-user/graphite/releases) - Migration guide: See `graphite.Migration` module documentation - More on pickle security: [Python docs – pickle security](https://docs.python.org/3/library/pickle.html#module-pickle)

GHSA-qw48-84f6-28gv Affected Graphitedb Versions

1 component(s)
Fixed Versions:
0.2
Product / Package Ecosystem Affected Versions Fixed Version
graphitedb
pypi/graphitedb
PyPI
< 0.2
0.2

References

GitHub Advisory / Wiki ADVISORY
https://github.com/mkh-user/graphite/security/advisories/GHSA-qw48-84f6-28gv
Graphitedb Source Repository REPOSITORY
https://github.com/mkh-user/graphite
Graphitedb Release RELEASE
https://github.com/mkh-user/graphite/releases/tag/v0.2

Frequently Asked Questions

What is GHSA-qw48-84f6-28gv?
GHSA-qw48-84f6-28gv is a security vulnerability in Graphitedb involving Graphite Has a Pickle Deserialization Vulnerability under CWE-502: Deserialization of Untrusted Data.
Which Graphitedb versions are affected?
Affected versions include releases prior to 0.2 across affected packages: graphitedb.
What version fixes GHSA-qw48-84f6-28gv?
Upgrading to 0.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is graphitedb affected?
Yes, graphitedb is affected in releases prior to 0.2. Upgrade your dependency to 0.2 or later.
What is the CVSS score of GHSA-qw48-84f6-28gv?
GHSA-qw48-84f6-28gv has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
What CWE is associated with GHSA-qw48-84f6-28gv?
GHSA-qw48-84f6-28gv is classified under CWE-502: Deserialization of Untrusted Data (The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.).
How can I check PyPI dependencies for GHSA-qw48-84f6-28gv?
Run the dependency tree command: 'pip show graphitedb'. 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
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-qw48-84f6-28gv",
  "modified" : "2026-05-18T13:27:56Z",
  "published" : "2026-05-18T13:27:55Z",
  "aliases" : [ ],
  "summary" : "Graphite Has a Pickle Deserialization Vulnerability",
  "details" : "### Impact\n**Type of vulnerability:** Insecure Deserialization via Python's `pickle` module.\n\n**Who is impacted:**  \nUsers of *Graphite graph database engine* versions **before 0.2** who load database files from untrusted or third-party sources.  \nAn attacker could craft a malicious database file that executes arbitrary code when loaded by the engine. This is possible because the engine used `pickle` for serialization, which is known to be unsafe for untrusted data.\n\n### Patches\nThe vulnerability has been patched starting from **version 0.2**.  \nAll users should upgrade to **version 0.2 or later** (the current version is 0.4 at publishing time).  \nIn version 0.2 and above, the engine uses **JSON** instead of `pickle` for database storage, eliminating the deserialization risk.\n\n### Workarounds\nIf users cannot upgrade immediately:\n\n1. **Do not load database files from untrusted or unknown sources** when using versions <0.2.\n2. **Migrate existing pickle-based databases** to the new JSON format using the provided migration module:\n\n```python\nfrom graphite.Migration import convert_pickle_to_json\nconvert_pickle_to_json(\"path/to/old_database.pkl\", \"path/to/new_database.json\")\n```\n\nAfter migration, you can safely use the database with version 0.2+.\n\n**Note:** Versions 0.2 and later will show a **warning** when attempting to load legacy pickle files, reminding you to migrate them. Also, **you can't load pickle files** in 0.2 and later.\n\n### Resources\n- Upgrade to [v0.2 or newer](https://github.com/mkh-user/graphite/releases)\n- Migration guide: See `graphite.Migration` module documentation\n- More on pickle security: [Python docs – pickle security](https://docs.python.org/3/library/pickle.html#module-pickle)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "graphitedb"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/mkh-user/graphite/security/advisories/GHSA-qw48-84f6-28gv"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/mkh-user/graphite"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/mkh-user/graphite/releases/tag/v0.2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-502" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-18T13:27:55Z",
    "nvd_published_at" : null
  }
}