How severe is GHSA-6437-7wc6-gmx5?

No CVSS score has been assigned to GHSA-6437-7wc6-gmx5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6437-7wc6-gmx5?

Affected package information for GHSA-6437-7wc6-gmx5 is not yet fully mapped. Check the official advisory links for details.

How do I fix GHSA-6437-7wc6-gmx5?

Upgrade the affected component to the fixed release for GHSA-6437-7wc6-gmx5, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.

How do I detect GHSA-6437-7wc6-gmx5 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate GHSA-6437-7wc6-gmx5 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-6437-7wc6-gmx5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6437-7wc6-gmx5 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-6437-7wc6-gmx5?

GHSA-6437-7wc6-gmx5 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 38th 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-6437-7wc6-gmx5?

GHSA-6437-7wc6-gmx5 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-6437-7wc6-gmx5 published, and has it been updated?

GHSA-6437-7wc6-gmx5 was published on November 3, 2026 and was last updated on November 5, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Label Studio before 1.23.2 SSRF and Token Disclosure via…

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk

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

Description

Label Studio before 1.23.2 (label-studio-sdk before 2.1.2) contains a server-side request forgery vulnerability that allows authenticated users to read internal URLs through image-bearing export formats. Attackers can import tasks with data.image pointing at internal services, export as YOLO or COCO with images to read responses, and spoof Host to capture the organization owner's API token.

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Fix
Upgrade the affected component to the fixed release for GHSA-6437-7wc6-gmx5, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.
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

Label Studio before 1.23.2 (label-studio-sdk before 2.1.2) contains a server-side request forgery vulnerability that allows authenticated users to read internal URLs through image-bearing export formats. Attackers can import tasks with data.image pointing at internal services, export as YOLO or COCO with images to read responses, and spoof Host to capture the organization owner's API token.

O3 Security · Impact-Aware SCA

Is GHSA-6437-7wc6-gmx5 in your dependencies?

Find it across your dependency tree, including transitive dependencies.

Scan my dependencies How O3 SCA works

Label Studio before 1.23.2 SSRF and Token Disclosure via Image Export DownloadsGHSA-6437-7wc6-gmx5

EPSS Exploitation Probability

Description

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-6437-7wc6-gmx5 in your dependencies?