Is symfony/polyfill-intl-idn 1.22 vulnerable?
Composer · 2 releases from 1.22.0 to 1.22.1 · latest symfony/polyfill-intl-idn is 1.43.0 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. symfony/polyfill-intl-idn 1.22.1, the last 1.22 release, is affected by 1 known security advisory (1 low), including CVE-2026-46644. Upgrade to 1.38.1 or later to fix all of them.
composer require symfony/polyfill-intl-idn:^1.38.1Is your project on an affected symfony/polyfill-intl-idn?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting symfony/polyfill-intl-idn 1.22.1
symfony/polyfill-intl-idn: xn-- labels with ASCII-only Punycode payloads are treated as equivalent to their decoded form
- Affected
- >=1.17.1 <1.38.1
- Fixed in
- 1.38.1
Every symfony/polyfill-intl-idn 1.22.x release
Affected: 1.22.0 to 1.22.1. Latest symfony/polyfill-intl-idn: 1.43.0.
| Version | Known advisories |
|---|---|
| symfony/polyfill-intl-idn 1.22.1 | CVE-2026-46644 |
| symfony/polyfill-intl-idn 1.22.0 | CVE-2026-46644 |
Which of your client projects are still on symfony/polyfill-intl-idn 1.22?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact symfony/polyfill-intl-idn version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other symfony/polyfill-intl-idn versions
- symfony/polyfill-intl-idn 1.25
- symfony/polyfill-intl-idn 1.24
- symfony/polyfill-intl-idn 1.23
- symfony/polyfill-intl-idn 1.20
- symfony/polyfill-intl-idn 1.19
- symfony/polyfill-intl-idn 1.18
- symfony/polyfill-intl-idn 1.43
- symfony/polyfill-intl-idn 1.42
- symfony/polyfill-intl-idn 1.38
- symfony/polyfill-intl-idn 1.37
- symfony/polyfill-intl-idn 1.36
- symfony/polyfill-intl-idn 1.35
- All symfony/polyfill-intl-idn advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.