# GHSA-qw48-84f6-28gv: Graphite Has a Pickle Deserialization Vulnerability


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 18 May 2026

## What is GHSA-qw48-84f6-28gv?

GHSA-qw48-84f6-28gv is a vulnerability in graphitedb, published on 18 May 2026. 

### Official description

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

## Which versions are affected by GHSA-qw48-84f6-28gv?

2 open source packages ship an affected version, including graphitedb.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `graphitedb` | PyPI | All versions | 0.2 |
| `graphitedb` | PyPI | All versions | 0.2 |

## How do I fix GHSA-qw48-84f6-28gv?

Upgrade graphitedb to 0.2 or later.

## Is GHSA-qw48-84f6-28gv being exploited?

There is no known exploitation of GHSA-qw48-84f6-28gv in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-qw48-84f6-28gv and fix it if it is affected.

What it is: GHSA-qw48-84f6-28gv is a vulnerability in graphitedb, published on 18 May 2026. 
Exploitation: There is no known exploitation of GHSA-qw48-84f6-28gv in the wild and no public exploit code.

Affected packages and fixed versions:
- graphitedb (PyPI): affected all versions; fixed in 0.2
- graphitedb (PyPI): affected all versions; fixed in 0.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-qw48-84f6-28gv/ (Markdown: https://insights.sbomify.com/GHSA-qw48-84f6-28gv/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-qw48-84f6-28gv

---
From sbomify Insights: https://insights.sbomify.com/GHSA-qw48-84f6-28gv/
Summaries are generated and may contain mistakes; the official description above is the record.
