Vulnerability Database · Packagist · Package report

microsoft/microsoft-graph: vulnerability history, versions and safety

microsoft/microsoft-graph is a package in the Packagist ecosystem. Vulert records 1 vulnerability for it across 96 releases, first recorded in Dec 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

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.

Vulert verdict on microsoft/microsoft-graph i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 05 Dec 2023. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 1 vulnerability on record across 1 year, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 05 Dec 2023 i
  • Highest CVSS 5.4 i
  • With no published fix 0 i

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 holds for microsoft/microsoft-graph, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
1.109.0 M1 Yes Details →
1.108.0 M1 Yes Details →
1.107.0 M1 Yes Details →
1.106.0 M1 Yes Details →
1.105.0 M1 Yes Details →
1.104.0 M1 Yes Details →
1.103.0 M1 Yes Details →
1.102.0 M1 Yes Details →
1.101.0 M1 Yes Details →
1.100.0 M1 Yes Details →
1.99.0 M1 Yes Details →
1.98.0 M1 Yes Details →
1.97.0 M1 Yes Details →
1.96.0 M1 Yes Details →
1.95.0 M1 Yes Details →
1.94.0 M1 Yes Details →
1.93.0 M1 Yes Details →
1.92.0 M1 Yes Details →
1.91.0 M1 Yes Details →
1.90.0 M1 Yes Details →
1.89.0 M1 Yes Details →
1.88.0 M1 Yes Details →
1.87.0 M1 Yes Details →
1.86.0 M1 Yes Details →
1.85.0 M1 Yes Details →
1.84.0 M1 Yes Details →
1.83.0 M1 Yes Details →
1.82.0 M1 Yes Details →
1.81.0 M1 Yes Details →
1.80.0 M1 Yes Details →
1.79.0 M1 Yes Details →
1.78.0 M1 Yes Details →
1.77.0 M1 Yes Details →
1.76.0 M1 Yes Details →
1.75.0 M1 Yes Details →
1.74.0 M1 Yes Details →
1.73.0 M1 Yes Details →
1.72.0 M1 Yes Details →
1.71.0 M1 Yes Details →
1.70.0 M1 Yes Details →
1.69.0 M1 Yes Details →
1.68.0 M1 Yes Details →
1.67.0 M1 Yes Details →
1.66.0 M1 Yes Details →
1.65.0 M1 Yes Details →
1.64.0 M1 Yes Details →
1.63.0 M1 Yes Details →
1.62.0 M1 Yes Details →
1.61.0 M1 Yes Details →
1.60.0 M1 Yes Details →
1.59.0 M1 Yes Details →
1.58.0 M1 Yes Details →
1.57.1 M1 Yes Details →
1.57.0 M1 Yes Details →
1.56.0 M1 Yes Details →
1.55.0 M1 Yes Details →
1.54.0 M1 Yes Details →
1.53.0 M1 Yes Details →
1.52.0 M1 Yes Details →
1.51.0 M1 Yes Details →
1.50.0 M1 Yes Details →
1.49.0 M1 Yes Details →
1.48.0 M1 Yes Details →
1.47.0 M1 Yes Details →
1.46.0 M1 Yes Details →
1.45.0 M1 Yes Details →
1.44.0 M1 Yes Details →
1.43.0 M1 Yes Details →
1.42.0 M1 Yes Details →
1.41.0 M1 Yes Details →
1.40.0 M1 Yes Details →
1.39.0 M1 Yes Details →
1.38.0 M1 Yes Details →
1.37.0 M1 Yes Details →
1.36.0 M1 Yes Details →
1.35.1 M1 Yes Details →
1.35.0 M1 Yes Details →
1.34.0 M1 Yes Details →
1.33.0 M1 Yes Details →
1.32.0 M1 Yes Details →
1.31.0 M1 Yes Details →
1.30.1 M1 Yes Details →
1.30.0 M1 Yes Details →
1.29.0 M1 Yes Details →
1.27.0 M1 Yes Details →
1.26.0 M1 Yes Details →
1.25.0 M1 Yes Details →
1.24.0 M1 Yes Details →
1.23.0 M1 Yes Details →
1.22.0 M1 Yes Details →
1.21.0 M1 Yes Details →
1.20.0 M1 Yes Details →
1.19.0 M1 Yes Details →
1.18.0 M1 Yes Details →
1.17.0 M1 Yes Details →
1.16.0 M1 Yes Details →

Newest 96 of 96 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1

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

03 Vulnerabilities

Recorded vulnerabilities for microsoft/microsoft-graph

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 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 microsoft/microsoft-graph

Is microsoft/microsoft-graph safe to use?

Vulert records 1 vulnerabilities for microsoft/microsoft-graph in Packagist: 0 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does microsoft/microsoft-graph have?

1 vulnerability is recorded for microsoft/microsoft-graph in the Packagist ecosystem: 0 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 microsoft/microsoft-graph vulnerabilities disclosed?

0 vulnerabilities were recorded for microsoft/microsoft-graph in the last 12 months, and the oldest entry in this database dates to 05 Dec 2023. 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 microsoft/microsoft-graph 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 microsoft/microsoft-graph for upcoming vulnerabilities?

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