GHSA-f7wr-f2gj-v69x json
Code injection through a RegExp's own source or flags property
published 14d ago modified 14d ago
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository lxsmnsyc/seroval. GitHub has not reviewed it into the GitHub Advisory Database and no CVE record has reached us yet, so everything here comes from the maintainers alone. Read the full advisory on GitHub.
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
Security advisory published by the maintainers of lxsmnsyc/seroval for seroval: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.
Patch / fix
- npm seroval 1.7.6
Is GHSA-f7wr-f2gj-v69x in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | seroval | <=1.7.5 |
1.7.6 |
Classification
References
Sources
- Maintainer advisory GHSA-f7wr-f2gj-v69x
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of lxsmnsyc/seroval published their own advisory on GitHub. Its facts and headline are shown here; the description stays on GitHub.