Vulnerability Database · Packagist · Package report

october/rain: vulnerability history, versions and safety

october/rain is a package in the Packagist ecosystem. Vulert records 6 vulnerabilities for it across 120 releases, from Aug 2020 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded C1 M5
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 14 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on october/rain i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 6 vulnerabilities on record across 5 years, 3 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 6 over 5 years · 3 in the last year i
  • Latest disclosure 14 Apr 2026 i
  • Highest CVSS 9.8 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 october/rain, 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
v4.1.9 M2 Yes Details →
v4.1.6 M2 Yes Details →
v4.1.5 M2 Yes Details →
v4.1.4 M3 Yes Details →
v4.1.1 M3 Yes Details →
v4.1.0 M3 Yes Details →
v4.0.22 M3 Yes Details →
v4.0.20 M3 Yes Details →
v4.0.16 M3 Yes Details →
v4.0.13 M3 Yes Details →
v4.0.12 M3 Yes Details →
v4.0.11 M3 Yes Details →
v4.0.10 M3 Yes Details →
v4.0.7 M3 Yes Details →
v4.0.6 M3 Yes Details →
v4.0.3 M3 Yes Details →
v4.0.2 M3 Yes Details →
v4.0.1 M3 Yes Details →
v4.0.0 M3 Yes Details →
v1.0.471 C1 Yes Details →
v1.0.470 C1 Yes Details →
v1.0.469 C1 Yes Details →
v1.0.468 C1 Yes Details →
v1.0.467 C1 M1 Yes Details →
v1.0.466 C1 M1 Yes Details →
v1.0.465 C1 M1 Yes Details →
v1.0.464 C1 M1 Yes Details →
v1.0.463 C1 M1 Yes Details →
v1.0.462 C1 M1 Yes Details →
v1.0.461 C1 M1 Yes Details →
v1.0.460 C1 M1 Yes Details →
v1.0.459 C1 M1 Yes Details →
v1.0.458 C1 M1 Yes Details →
v1.0.457 C1 M1 Yes Details →
v1.0.456 C1 M1 Yes Details →
v1.0.455 C1 M1 Yes Details →
v1.0.454 C1 M1 Yes Details →
v1.0.453 C1 M1 Yes Details →
v1.0.452 C1 M1 Yes Details →
v1.0.451 C1 M1 Yes Details →
v1.0.450 C1 M1 Yes Details →
v1.0.449 C1 M1 Yes Details →
v1.0.448 C1 M1 Yes Details →
v1.0.447 C1 M1 Yes Details →
v1.0.446 C1 M1 Yes Details →
v1.0.445 C1 M1 Yes Details →
v1.0.444 C1 M1 Yes Details →
v1.0.443 C1 M1 Yes Details →
v1.0.442 C1 M1 Yes Details →
v1.0.441 C1 M1 Yes Details →
v1.0.440 C1 M1 Yes Details →
v1.0.439 C1 M1 Yes Details →
v1.0.438 C1 M1 Yes Details →
v1.0.437 C1 M1 Yes Details →
v1.0.436 C1 M1 Yes Details →
v1.0.435 C1 M1 Yes Details →
v1.0.434 C1 M1 Yes Details →
v1.0.433 C1 M1 Yes Details →
v1.0.432 C1 M1 Yes Details →
v1.0.431 C1 M1 Yes Details →
v1.0.430 C1 M1 Yes Details →
v1.0.429 C1 M1 Yes Details →
v1.0.428 C1 M1 Yes Details →
v1.0.427 C1 M1 Yes Details →
v1.0.426 C1 M1 Yes Details →
v1.0.425 C1 M2 Yes Details →
v1.0.424 C1 M2 Yes Details →
v1.0.423 C1 M2 Yes Details →
v1.0.422 C1 M2 Yes Details →
v1.0.421 C1 M2 Yes Details →
v1.0.420 C1 M2 Yes Details →
v1.0.419 C1 M2 Yes Details →
v1.0.418 C1 M2 Yes Details →
v1.0.417 C1 M2 Yes Details →
v1.0.416 C1 M2 Yes Details →
v1.0.415 C1 M2 Yes Details →
v1.0.414 C1 M2 Yes Details →
v1.0.413 C1 M2 Yes Details →
v1.0.412 C1 M2 Yes Details →
v1.0.411 C1 M2 Yes Details →
v1.0.410 C1 M2 Yes Details →
v1.0.409 C1 M2 Yes Details →
v1.0.408 C1 M2 Yes Details →
v1.0.407 C1 M2 Yes Details →
v1.0.406 C1 M2 Yes Details →
v1.0.405 C1 M2 Yes Details →
v1.0.404 C1 M2 Yes Details →
v1.0.403 C1 M2 Yes Details →
v1.0.402 C1 M2 Yes Details →
v1.0.401 C1 M2 Yes Details →
v1.0.400 C1 M2 Yes Details →
v1.0.399 C1 M2 Yes Details →
v1.0.398 C1 M2 Yes Details →
v1.0.397 C1 M2 Yes Details →
v1.0.396 C1 M2 Yes Details →
v1.0.395 C1 M2 Yes Details →
v1.0.394 C1 M2 Yes Details →
v1.0.393 C1 M2 Yes Details →
v1.0.392 C1 M2 Yes Details →
v1.0.391 C1 M2 Yes Details →
v1.0.390 C1 M2 Yes Details →
v1.0.389 C1 M2 Yes Details →
v1.0.388 C1 M2 Yes Details →
v1.0.387 C1 M2 Yes Details →
v1.0.386 C1 M2 Yes Details →
v1.0.385 C1 M2 Yes Details →
v1.0.384 C1 M2 Yes Details →
v1.0.383 C1 M2 Yes Details →
v1.0.382 C1 M2 Yes Details →
v1.0.381 C1 M2 Yes Details →
v1.0.380 C1 M2 Yes Details →
v1.0.379 C1 M2 Yes Details →
v1.0.378 C1 M2 Yes Details →
v1.0.377 C1 M2 Yes Details →
v1.0.376 C1 M2 Yes Details →
v1.0.375 C1 M2 Yes Details →
v1.0.374 C1 M2 Yes Details →
v1.0.373 C1 M2 Yes Details →
v1.0.372 C1 M2 Yes Details →
v1.0.371 C1 M2 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2021 1
  • 2022 1
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for october/rain

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 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 october/rain

Is october/rain safe to use?

Vulert records 6 vulnerabilities for october/rain in Packagist: 1 critical, 0 high, 5 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 october/rain have?

6 vulnerabilities are recorded for october/rain in the Packagist ecosystem: 1 critical, 0 high, 5 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 october/rain vulnerabilities disclosed?

3 vulnerabilities were recorded for october/rain in the last 12 months, and the oldest entry in this database dates to 05 Aug 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 october/rain 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 october/rain for upcoming vulnerabilities?

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