How severe is GHSA-67m4-qxp3-j6hh?

GHSA-67m4-qxp3-j6hh has a CVSS score of 8.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-67m4-qxp3-j6hh?

GHSA-67m4-qxp3-j6hh affects the following packages: TrueLayer.Client (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-67m4-qxp3-j6hh?

Update TrueLayer.Client to 1.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-67m4-qxp3-j6hh is resolved across your whole dependency graph.

How do I detect GHSA-67m4-qxp3-j6hh in my NuGet dependencies?

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

How do I mitigate GHSA-67m4-qxp3-j6hh if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is GHSA-67m4-qxp3-j6hh actively exploited in the wild?

No public exploit code has been indexed for GHSA-67m4-qxp3-j6hh 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-67m4-qxp3-j6hh?

GHSA-67m4-qxp3-j6hh has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 45th 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-67m4-qxp3-j6hh?

GHSA-67m4-qxp3-j6hh is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-67m4-qxp3-j6hh published, and has it been updated?

GHSA-67m4-qxp3-j6hh was published on January 30, 2024 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET

.NET NuGet

Not in CISA KEV

HIGH severity

TrueLayer.Client SSRF when fetching payment or payment providerGHSA-67m4-qxp3-j6hh

HIGHFix: TrueLayer/truelayer-dotnet@75e436e

GHSA-67m4-qxp3-j6hh is a high-severity (CVSS 8.6) Server-Side Request Forgery (SSRF) vulnerability in TrueLayer.Client. A fix is available for TrueLayer.Client — see the affected versions and patch details below.

Also known asCVE-2024-23838

Published

Jan 30, 2024

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-67m4-qxp3-j6hh.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs45th percentile — riskier than 45% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

.NETTrueLayer.Client

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

TrueLayer.NET is the .Net client for TrueLayer. The vulnerability could potentially allow a malicious actor to gain control over the destination URL of the HttpClient used in the API classes. For applications using the SDK, requests to unexpected resources on local networks or to the internet could be made which could lead to information disclosure. The issue can be mitigated by having strict egress rules limiting the destinations to which requests can be made, and applying strict validation to any user input passed to the truelayer-dotnet library. Versions of TrueLayer.Client v1.6.0 and later are not affected.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`TrueLayer.Client`	all versions	1.6.0`dotnet add package TrueLayer.Client --version 1.6.0`

Affected Products

1 product · 1 configurations

Application

truelayer.nettruelayer

< 1.6.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for TrueLayer.Client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update TrueLayer.Client to 1.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-67m4-qxp3-j6hh is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

### Impact The vulnerability could potentially allow a malicious actor to gain control over the destination URL of the HttpClient used in the API classes. For applications using the SDK, requests to unexpected resources on local networks or to the internet could be made which could lead to information disclosure. ### Patches Versions of TrueLayer.Client `v1.6.0` and later are not affected. ### Workarounds The issue can be mitigated by having strict egress rules limiting the destinations to which requests can be made, and applying strict validation to any user input passed to the TrueLayer.Cl