How severe is GHSA-3x5x-fw77-g54c?

No CVSS score has been assigned to GHSA-3x5x-fw77-g54c yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3x5x-fw77-g54c?

GHSA-3x5x-fw77-g54c affects the following packages: dgl (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-3x5x-fw77-g54c?

The records we use list no patched version of dgl for GHSA-3x5x-fw77-g54c. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-3x5x-fw77-g54c in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dgl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-3x5x-fw77-g54c if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is GHSA-3x5x-fw77-g54c actively exploited in the wild?

No public exploit code has been indexed for GHSA-3x5x-fw77-g54c yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-3x5x-fw77-g54c published, and has it been updated?

GHSA-3x5x-fw77-g54c was published on March 5, 2025 and was last updated on March 5, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

dmlc/dgl Vulnerable to Remote Code Execution by Pickle Deserialization via rpc.recv_request()GHSA-3x5x-fw77-g54c

GHSA-3x5x-fw77-g54c is a remote code execution vulnerability in dgl. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Published

Mar 5, 2025

Updated

Mar 5, 2025

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Mar 5, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍dgl

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Dgl implements rpc server (start_server() in rpc_server.py) for supporting the RPC communications among different remote users over networks. It relies on pickle serialize and deserialize to pack and unpack network messages. The is a known risk in pickle deserialization functionality that can be used for remote code execution.

Patches

TBD.

Workarounds

When running DGL distributed training and inference (DistDGL) make sure you do not assign public IPs to any instance in the cluster.

References

Issue #7874

Reported by

Pinji Chen ([email protected]) from NISL lab (https://netsec.ccert.edu.cn/about) at Tsinghua University

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`dgl`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dgl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of dgl for GHSA-3x5x-fw77-g54c. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

### Impact Dgl implements rpc server (start_server() in rpc_server.py) for supporting the RPC communications among different remote users over networks. It relies on pickle serialize and deserialize to pack and unpack network messages. The is a known risk in pickle deserialization functionality that can be used for remote code execution. ### Patches TBD. ### Workarounds When running DGL distributed training and inference (DistDGL) make sure you do not assign public IPs to any instance in the cluster. ### References Issue #7874 ### Reported by Pinji Chen ([[email protected]](mailt

O3 Security · Impact-Aware SCA

Is GHSA-3x5x-fw77-g54c in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works