GHSA-g3rh-rrhp-jhh9
LOWSymfony has an incorrect response from Validator when input ends with `\n`
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
symfony/symfony🐘symfony/symfony🐘symfony/symfony🐘symfony/validator🐘symfony/validator🐘symfony/validatorReal-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
Description
It is possible to trick a Validator configured with a regular expression using the $ metacharacters, with an input ending with \n.
Resolution
Symfony now uses the D regex modifier to match the entire input.
The patch for this issue is available here for branch 5.4.
Credits
We would like to thank Offscript for reporting the issue and Alexandre Daubois for providing the fix.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | symfony/symfony | all versions | 5.4.43 |
| 🐘Packagist | symfony/symfony | ≥ 6.0.0&&< 6.4.11 | 6.4.11 |
| 🐘Packagist | symfony/symfony | ≥ 7.0.0&&< 7.1.4 | 7.1.4 |
| 🐘Packagist | symfony/validator | all versions | 5.4.43 |
| 🐘Packagist | symfony/validator | ≥ 6.0.0&&< 6.4.11 | 6.4.11 |
| 🐘Packagist | symfony/validator | ≥ 7.0.0&&< 7.1.4 | 7.1.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/symfony. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update symfony/symfony to 5.4.43 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g3rh-rrhp-jhh9 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.
How O3 protects you
O3 pinpoints whether GHSA-g3rh-rrhp-jhh9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-g3rh-rrhp-jhh9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-g3rh-rrhp-jhh9 in your dependencies?
O3 detects GHSA-g3rh-rrhp-jhh9 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.