Vulnerability Database · npm · abortcontroller-polyfill · Version

abortcontroller-polyfill 1.2.8

No vulnerabilities in this database cover 1.2.8.

Every vulnerability Vulert holds for abortcontroller-polyfill was tested against this version and none of them covers it. That is the good answer, not a guarantee — the package page shows which versions are affected.

Critical 0 High 0 Medium 0 Low 0 Unrated 0

Released 11 Mar 2019 Licence MIT Also known from other sources 0 Newer releases 43 Database updated 23/Oct/2026

Release and licence data published by the npm registry. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Vulnerabilities affecting this version

abortcontroller-polyfill 1.2.8 vulnerabilities

No vulnerability in the Vulert database covers abortcontroller-polyfill 1.2.8. See the versions that are affected →

Looking for another version, or everything Vulert holds for abortcontroller-polyfill?

All versions → Full vulnerability list →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About abortcontroller-polyfill 1.2.8

Is abortcontroller-polyfill 1.2.8 vulnerable?

No. No vulnerability in the Vulert database covers abortcontroller-polyfill 1.2.8. Every vulnerability Vulert holds for abortcontroller-polyfill was tested against this release and none of them covers it — the good answer, though not a guarantee, since new vulnerabilities are published for packages all the time.

Is 1.2.8 the latest release of abortcontroller-polyfill?

No. 1.2.8 was published 11 Mar 2019, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

How do I monitor abortcontroller-polyfill for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the abortcontroller-polyfill version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.