How severe is GHSA-4cv2-4hjh-77rx?

No CVSS score has been assigned to GHSA-4cv2-4hjh-77rx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4cv2-4hjh-77rx?

GHSA-4cv2-4hjh-77rx affects the following packages: System.Linq.Dynamic.Core (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-4cv2-4hjh-77rx?

Update System.Linq.Dynamic.Core to 1.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4cv2-4hjh-77rx is resolved across your whole dependency graph.

How do I detect GHSA-4cv2-4hjh-77rx in my NuGet dependencies?

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

How do I mitigate GHSA-4cv2-4hjh-77rx if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-4cv2-4hjh-77rx actively exploited in the wild?

No public exploit code has been indexed for GHSA-4cv2-4hjh-77rx 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.

What is the EPSS score for GHSA-4cv2-4hjh-77rx?

GHSA-4cv2-4hjh-77rx has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 28th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-4cv2-4hjh-77rx?

GHSA-4cv2-4hjh-77rx is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-4cv2-4hjh-77rx published, and has it been updated?

GHSA-4cv2-4hjh-77rx was published on January 21, 2025 and was last updated on January 27, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET NuGet

Not in CISA KEV

Property reflection in System.Linq.Dynamic.CoreGHSA-4cv2-4hjh-77rx

Fix: zzzprojects/System.Linq.Dynamic.Core@49b6cf0

GHSA-4cv2-4hjh-77rx is a CWE-863 vulnerability in System.Linq.Dynamic.Core. A fix is available for System.Linq.Dynamic.Core — see the affected versions and patch details below.

Also known asCVE-2024-51417

Published

Jan 21, 2025

Updated

Jan 27, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-4cv2-4hjh-77rx.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs28th percentile — riskier than 28% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

.NETSystem.Linq.Dynamic.Core

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

Description

An issue in System.Linq.Dynamic.Core versions before v.1.6.0 allow remote access to properties on reflection types and static properties/fields.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`System.Linq.Dynamic.Core`	all versions	1.6.0`dotnet add package System.Linq.Dynamic.Core --version 1.6.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for System.Linq.Dynamic.Core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update System.Linq.Dynamic.Core to 1.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4cv2-4hjh-77rx is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.