VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@a2ui/web_core: vulnerability history, versions and safety

@a2ui/web_core is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 20 releases, from Aug 2026 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C1 M1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
2 in the last 12 months

Most recent disclosure 02 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @a2ui/web_core vulnerabilities

Vulert verdict on @a2ui/web_core 0.14.0 i

Updated on 23 Oct 2026

Careful: 0.14.0 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 0.14.0 — affected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 02 Oct 2026 i
  • Highest CVSS 9.3 i
  • With no published fix 1 i
  • Depended on by 7 packages i
  • Stars 16,761 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for @a2ui/web_core, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.14.0 17 Oct 2026 M1 Apache-2.0 No Details →
0.13.0 09 Oct 2026 M1 Apache-2.0 No Details →
0.12.0 28 Sep 2026 M1 Apache-2.0 No Details →
0.11.0 12 Sep 2026 M1 Apache-2.0 No Details →
0.10.7 01 Sep 2026 M1 Apache-2.0 No Details →
0.10.6 03 Aug 2026 M1 Apache-2.0 No Details →
0.10.5 17 Jul 2026 M1 Apache-2.0 No Details →
0.10.4 08 Jul 2026 M1 Apache-2.0 No Details →
0.10.3 22 Jun 2026 M1 Apache-2.0 No Details →
0.10.2 19 Jun 2026 M1 Apache-2.0 No Details →
0.10.1 17 Jun 2026 C1 M1 Apache-2.0 No Details →
0.10.0 12 May 2026 C1 M1 Apache-2.0 No Details →
0.9.2 17 Apr 2026 C1 M1 Apache-2.0 No Details →
0.9.1 16 Apr 2026 C1 M1 Apache-2.0 No Details →
0.9.1-alpha.4 15 Apr 2026 C1 M1 Apache-2.0 No Details →
0.9.1-alpha.3 14 Apr 2026 C1 M1 Apache-2.0 No Details →
0.9.1-alpha.2 14 Apr 2026 C1 M1 Apache-2.0 No Details →
0.9.1-alpha.1 14 Apr 2026 C1 M1 Apache-2.0 No Details →
0.9.1-alpha.0 09 Apr 2026 C1 M1 Apache-2.0 No Details →
0.9.0 27 Mar 2026 C1 M1 Apache-2.0 No Details →
0.8.0 04 Mar 2026 none Apache-2.0 — Details →

All 21 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for @a2ui/web_core

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-10032: @a2ui/web_core Critical XSS Vulnerability via openUrl Function 9.3 critical 0.10.2 02 Oct 2026
Critical XSS Vulnerability in @a2ui/web_core: openUrl Function Allows JavaScript Execution 6.1 medium No fix published 04 Aug 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 @a2ui/web_core

Is @a2ui/web_core safe to use?

Vulert records 2 vulnerabilities for @a2ui/web_core in npm: 1 critical, 0 high, 1 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is @a2ui/web_core's Vulert package health score?

Vulert scores @a2ui/web_core 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of @a2ui/web_core affected?

Yes. 0.14.0, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does @a2ui/web_core have?

2 vulnerabilities are recorded for @a2ui/web_core in the npm ecosystem: 1 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @a2ui/web_core vulnerabilities disclosed?

2 vulnerabilities were recorded for @a2ui/web_core in the last 12 months, and the oldest entry in this database dates to 04 Aug 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of @a2ui/web_core are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor @a2ui/web_core for upcoming vulnerabilities?

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