VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

hobbes: vulnerability history, versions and safety

hobbes is a package in the OSS-Fuzz ecosystem. Vulert records 2 vulnerabilities for it across 2 affected ranges, 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 H1 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 17 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all hobbes vulnerabilities

Vulert verdict on hobbes i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 2 vulnerabilities on record across 1 year, 2 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 2 over 1 year · 2 in the last year i
  • Latest disclosure 17 Oct 2026 i
  • Highest CVSS n/a 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

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
from bd8cb86615562113ae09e837b8447d22dd945e80 up to 3d08bc2cd3474bb3c41bfb21dc3c7b0b1109e5e7 (exclusive) 1
from b04da9e612f6d0bdd9d691c0396ae481dbfc6da9 up to bff061afc31cfc460f38dd9c5c4b754b72b88de5 (exclusive) 1

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 hobbes

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap Buffer Overflow Vulnerability in Hobbes Package N/A high 3d08bc2cd3474bb3c41bfb21dc3c7b0b1109e5e7 25 Aug 2026
Critical UNKNOWN READ Vulnerability in hobbes Package N/A medium bff061afc31cfc460f38dd9c5c4b754b72b88de5 17 Oct 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 hobbes

Is hobbes safe to use?

Vulert records 2 vulnerabilities for hobbes in OSS-Fuzz: 0 critical, 1 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 hobbes have?

2 vulnerabilities are recorded for hobbes in the OSS-Fuzz ecosystem: 0 critical, 1 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 hobbes vulnerabilities disclosed?

2 vulnerabilities were recorded for hobbes in the last 12 months, and the oldest entry in this database dates to 25 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 hobbes 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 hobbes for upcoming vulnerabilities?

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