Vulnerability Database · OSS-Fuzz · Package report

grok: vulnerability history, versions and safety

grok is a package in the OSS-Fuzz ecosystem. Vulert records 31 vulnerabilities for it across 61 releases, from Nov 2020 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
31 vulnerabilities recorded H13 M15 U3
i
13 with no fix published

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

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

Most recent disclosure 30 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on grok i

Updated on 23 Oct 2026

Careful: 13 of the 31 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 31 vulnerabilities on record across 5 years, 6 in the last year.

What to do: Plan around the 13 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 31 over 5 years · 6 in the last year i
  • Latest disclosure 30 Jul 2026 i
  • Highest CVSS n/a i
  • With no published fix 13 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 grok, 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
v20.3.7 M1 Yes Details →
v20.3.6 H2 M1 Yes Details →
v20.3.5 H2 M1 Yes Details →
v20.3.4 H1 Yes Details →
v20.3.3 H1 Yes Details →
v20.3.2 H1 Yes Details →
v20.3.1 H1 Yes Details →
v20.3.0 H1 Yes Details →
v20.2.9 H1 Yes Details →
v20.2.8 H1 Yes Details →
v20.2.7 H1 Yes Details →
v20.2.6 H1 Yes Details →
v20.2.5 H1 Yes Details →
v20.2.4 H1 Yes Details →
v20.2.3 H1 Yes Details →
v20.2.2 H1 Yes Details →
v20.2.1 H1 Yes Details →
v20.2.0 H2 Yes Details →
v20.1.0 H2 Yes Details →
v10.0.8 H3 M8 U1 No Details →
v10.0.7 H3 M8 U1 No Details →
v10.0.6 H4 M8 U1 No Details →
v10.0.5 H4 M8 U1 No Details →
v10.0.5.debian H4 M8 U1 No Details →
v10.0.4 H4 M8 U1 No Details →
v10.0.3 H4 M8 U1 No Details →
v10.0.2 H4 M8 U1 No Details →
v10.0.1 H4 M8 U1 No Details →
v10.0.0 H4 M8 U1 No Details →
v10.0.0.debian H3 M8 U1 No Details →
v9.7.8 H5 M7 U1 No Details →
v9.7.7 H3 M7 U1 No Details →
v9.7.6 H3 M7 U2 No Details →
v9.7.5 H3 M5 U1 No Details →
v9.7.5.debian H3 M7 U2 No Details →
v9.7.4 H3 M7 No Details →
v9.7.4.debian H2 M2 No Details →
v9.7.3 H3 M6 No Details →
v9.7.2 H3 M6 No Details →
v9.7.1 H3 M3 No Details →
v9.7.0 H3 M3 No Details →
v9.6.0 H3 M3 No Details →
v9.5.0 H3 M3 No Details →
v9.5.0.debian H3 M3 No Details →
v9.4.0 H2 M3 No Details →
v9.3.0 H2 M3 No Details →
v9.2.0 H2 M3 No Details →
v9.1.0 H2 M3 No Details →
v9.0.0 H2 M3 No Details →
v8.0.3 H2 M3 No Details →
v8.0.2 H2 M3 No Details →
v8.0.1 H2 M3 No Details →
v8.0.0 H2 No Details →
v7.6.6-3 H1 No Details →
v7.6.6 H1 No Details →
v7.6.6.debian H1 No Details →
v7.6.5 M1 No Details →
v7.6.5.debian M1 No Details →
v7.6.4 M1 No Details →
v7.6.3 M1 No Details →
v7.6.2 M1 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 2
  • 2021 10
  • 2022 11
  • 2023 2
  • 2026 6

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

03 Vulnerabilities

Recorded vulnerabilities for grok

The 5 most severe of 31 vulnerabilities recorded for this package

Search all 31 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Stack-use-after-return vulnerability in grok N/A unrated No fix published 11 Apr 2022
Stack-use-after-scope vulnerability in grok N/A unrated 12ef5ef65d81862f0dcad9fafdbabb3c93a72934 09 Apr 2022
Use-of-uninitialized-value in grok: N_SSE4::vscheduler<DecompressDcShiftIrrev> N/A medium No fix published 02 Apr 2022
Heap-buffer-overflow in grok::FileFormatDecompress::apply_palette_clr N/A high No fix published 23 Apr 2021
Heap Buffer Overflow Vulnerability in Grok Package N/A medium 553b008061c8fafcb161ae293f489e08abf2e2d1 30 Jul 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 grok

Is grok safe to use?

Vulert records 31 vulnerabilities for grok in OSS-Fuzz: 0 critical, 13 high, 15 medium and 0 low, plus 3 not yet rated. 13 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does grok have?

31 vulnerabilities are recorded for grok in the OSS-Fuzz ecosystem: 0 critical, 13 high, 15 medium and 0 low, plus 3 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 grok vulnerabilities disclosed?

6 vulnerabilities were recorded for grok in the last 12 months, and the oldest entry in this database dates to 28 Nov 2020. 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 grok 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 grok for upcoming vulnerabilities?

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