How severe is GHSA-78hm-5hjw-58mh?

No CVSS score has been assigned to GHSA-78hm-5hjw-58mh yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-78hm-5hjw-58mh?

GHSA-78hm-5hjw-58mh affects the following packages: ua-parser/uap-php (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-78hm-5hjw-58mh?

Update ua-parser/uap-php to 3.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-78hm-5hjw-58mh is resolved across your whole dependency graph.

How do I detect GHSA-78hm-5hjw-58mh in my Packagist dependencies?

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

How do I mitigate GHSA-78hm-5hjw-58mh if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-78hm-5hjw-58mh actively exploited in the wild?

No public exploit code has been indexed for GHSA-78hm-5hjw-58mh 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-78hm-5hjw-58mh published, and has it been updated?

GHSA-78hm-5hjw-58mh was published on June 7, 2024 and was last updated on December 4, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

ua-parser/uap-php ReDoS vulnerabilityGHSA-78hm-5hjw-58mh

Fix: ua-parser/uap-core#363

GHSA-78hm-5hjw-58mh is a security vulnerability in ua-parser/uap-php. A fix is available for ua-parser/uap-php — see the affected versions and patch details below.

Published

Jun 7, 2024

Updated

Dec 4, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 4, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘ua-parser/uap-php

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

Description

A regex expression in ua-parser/uap-php could lead to a ReDoS vulnerability in versions prior to 3.8.0.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ua-parser/uap-php`	all versions	3.8.0`composer require ua-parser/uap-php:^3.8.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ua-parser/uap-php, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ua-parser/uap-php to 3.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-78hm-5hjw-58mh is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

A regex expression in ua-parser/uap-php could lead to a ReDoS vulnerability in versions prior to 3.8.0.

O3 Security · Impact-Aware SCA

Is GHSA-78hm-5hjw-58mh in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works