VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

mxgraph: vulnerability history, versions and safety

mxgraph is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 30 releases, from May 2022 to Oct 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C1 M2
i
1 with no fix published

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

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

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mxgraph vulnerabilities

Vulert verdict on mxgraph 4.2.2 i

Updated on 23 Oct 2026

Careful: 4.2.2 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 44/100
  • Security Some issues to review
  • Maintenance Deprecated
  • Popularity Widely used
  • Community Quiet

The registry marks the latest release as deprecated, 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 4.2.2 — affected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 12 Oct 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Depended on by 94 packages i
  • Stars 6,901 i
  • OpenSSF scorecard 0/10 i
  • Last release 71 months ago 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 mxgraph, 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
4.2.2 28 Oct 2020 M1 Apache-2.0 No Details →
4.2.1 28 Oct 2020 M1 Apache-2.0 No Details →
4.2.0 19 Jun 2020 M1 Apache-2.0 No Details →
4.1.1 31 Mar 2020 M1 Apache-2.0 No Details →
4.1.0 24 Jan 2020 M1 Apache-2.0 No Details →
4.0.6 08 Nov 2019 M1 Apache-2.0 No Details →
4.0.5 17 Oct 2019 M1 Apache-2.0 No Details →
4.0.4 20 Aug 2019 M1 Apache-2.0 No Details →
4.0.3 26 Jul 2019 M1 Apache-2.0 No Details →
4.0.2 15 Jul 2019 M1 Apache-2.0 No Details →
4.0.1 03 Jul 2019 M1 Apache-2.0 No Details →
3.9.12 24 Dec 2018 M2 Apache-2.0 No Details →
3.9.11 06 Nov 2018 M2 Apache-2.0 No Details →
3.9.8 06 Jul 2018 M2 Apache-2.0 No Details →
3.9.7 22 Jun 2018 M2 Apache-2.0 No Details →
3.9.6 31 May 2018 M2 Apache-2.0 No Details →
3.9.5 24 May 2018 M2 Apache-2.0 No Details →
3.9.4 17 May 2018 M2 Apache-2.0 No Details →
3.9.3 05 Mar 2018 M2 Apache-2.0 No Details →
3.9.2 28 Feb 2018 M2 Apache-2.0 No Details →
3.9.1 27 Jan 2018 M2 Apache-2.0 No Details →
3.9.0 19 Jan 2018 M2 Apache-2.0 No Details →
3.8.0 30 Nov 2017 M2 Apache-2.0 No Details →
3.7.6 24 Nov 2017 M2 Apache-2.0 No Details →
3.7.5 28 Aug 2017 C1 M2 Apache-2.0 No Details →
3.7.4 27 Jun 2017 C1 M2 Apache-2.0 No Details →
3.7.3 27 Jun 2017 C1 M2 Apache-2.0 No Details →
3.7.2-2 12 Apr 2017 C1 M2 Apache-2.0 No Details →
3.7.2-1 12 Apr 2017 C1 M2 Apache-2.0 No Details →
3.7.1 09 Mar 2017 C1 M2 Apache-2.0 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 3

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

03 Vulnerabilities

Recorded vulnerabilities for mxgraph

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
Vulnerability in mxGraph: XXE Attacks 9.8 critical 3.7.6 14 May 2022
Cross-Site Scripting Vulnerability in mxGraph 6.1 medium No fix published 12 Oct 2022
mxGraph vulnerable to cross-site scripting in color field 6.1 medium 4.0.1 24 May 2022

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 mxgraph

Is mxgraph safe to use?

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

What is mxgraph's Vulert package health score?

Vulert scores mxgraph 44/100, which reads as risky. 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 registry marks the latest release as deprecated, which caps this score.

Is the latest version of mxgraph affected?

Yes. 4.2.2, 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.

Which version of mxgraph should I use?

4.2.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does mxgraph have?

3 vulnerabilities are recorded for mxgraph in the npm ecosystem: 1 critical, 0 high, 2 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 mxgraph vulnerabilities disclosed?

0 vulnerabilities were recorded for mxgraph in the last 12 months, and the oldest entry in this database dates to 14 May 2022. 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 mxgraph 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 mxgraph for upcoming vulnerabilities?

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