Is symfony/polyfill-intl-idn 1.30 vulnerable?

Composer · 1 release from 1.30.0 to 1.30.0 · latest symfony/polyfill-intl-idn is 1.43.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. symfony/polyfill-intl-idn 1.30.0, the last 1.30 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.

Upgrade with:composer require symfony/polyfill-intl-idn:^1.38.1

Is your project on an affected symfony/polyfill-intl-idn?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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.30.0

  • LowCVE-2026-46644GHSA-2xf4-cg6j-vhgq28 May 2026

    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

Which of your client projects are still on symfony/polyfill-intl-idn 1.30?

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

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.