Vulnerability Database · PyPI · Package report

graphite-web: vulnerability history, versions and safety

graphite-web is a package in the PyPI ecosystem. Vulert records 13 vulnerabilities for it across 27 releases, from Sep 2013 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
13 vulnerabilities recorded C2 H1 M3 U7
i
6 with no fix published

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

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

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on graphite-web 1.1.10 i

Updated on 23 Oct 2026

Careful: 1.1.10 has 6 known vulnerabilities, and 6 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 41/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Not enough data

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 1.1.10 — affected i
  • Vulnerabilities on record 13 over 12 years · 3 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 9.0 i
  • With no published fix 6 i
  • Last release 53 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, 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 graphite-web, 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
1.1.10 22 May 2022 M3 U3 Apache-2.0 No Details →
1.1.8 19 Apr 2021 M3 U3 Apache-2.0 No Details →
1.1.7 16 Mar 2020 M3 U3 Apache-2.0 No Details →
1.1.6 25 Oct 2019 M3 U3 Apache-2.0 No Details →
1.1.5 23 Dec 2018 H1 M3 U4 Apache-2.0 No Details →
1.1.4 03 Sep 2018 H1 M3 U4 Apache-2.0 No Details →
1.1.3 04 Apr 2018 H1 M3 U4 Apache-2.0 No Details →
1.1.2 13 Feb 2018 H1 M3 U4 Apache-2.0 No Details →
1.1.1 19 Dec 2017 H1 M3 U4 Apache-2.0 No Details →
1.1.0 19 Dec 2017 H1 M3 U4 Apache-2.0 No Details →
1.0.2 11 Jul 2017 H1 M3 U4 Apache-2.0 No Details →
1.0.1 23 Apr 2017 H1 M3 U4 Apache-2.0 No Details →
1.0.0 11 Apr 2017 H1 M3 U4 Apache-2.0 No Details →
0.9.16 11 Apr 2017 H1 M3 U4 Apache-2.0 No Details →
0.9.15 27 Nov 2015 H1 M3 U4 Apache-2.0 No Details →
0.9.14 08 Nov 2015 H1 M3 U4 Apache-2.0 No Details →
0.9.13 31 Dec 2014 H1 M3 U4 Apache-2.0 No Details →
0.9.12 22 Aug 2013 H1 M3 U4 Apache-2.0 No Details →
0.9.11 20 Aug 2013 H1 M3 U4 Apache-2.0 No Details →
0.9.10 31 May 2012 C2 H1 M3 U7 Apache-2.0 No Details →
0.9.9 06 Oct 2011 C2 H1 M3 U7 Apache-2.0 No Details →
0.9.8 04 Apr 2011 C2 H1 M3 U7 Apache-2.0 No Details →
0.9.7rc0 17 Jan 2011 C2 H1 M3 U7 Apache-2.0 No Details →
0.9.7b0 12 Jan 2011 C2 H1 M3 U7 Apache-2.0 No Details →
0.9.7 08 Jan 2011 C2 H1 M3 U7 Apache-2.0 No Details →
0.9.6 26 Feb 2010 C2 H1 M3 U7 Apache-2.0 No Details →
0.9.5 07 Jan 2010 C2 H1 M3 U7 Apache-2.0 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2013 3
  • 2019 2
  • 2022 5
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for graphite-web

The 5 most severe of 13 vulnerabilities recorded for this package

Search all 13 in the database →

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 graphite-web

Is graphite-web safe to use?

Vulert records 13 vulnerabilities for graphite-web in PyPI: 2 critical, 1 high, 3 medium and 0 low, plus 7 not yet rated. 6 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is graphite-web's Vulert package health score?

Vulert scores graphite-web 41/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 current release has a vulnerability with no published fix, which caps this score.

Is the latest version of graphite-web affected?

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

Which version of graphite-web should I use?

1.1.10 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 graphite-web have?

13 vulnerabilities are recorded for graphite-web in the PyPI ecosystem: 2 critical, 1 high, 3 medium and 0 low, plus 7 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new graphite-web vulnerabilities disclosed?

3 vulnerabilities were recorded for graphite-web in the last 12 months, and the oldest entry in this database dates to 27 Sep 2013. 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 graphite-web 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 graphite-web for upcoming vulnerabilities?

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