Is laravel/framework 13.18 vulnerable?

Composer · 2 releases from 13.18.0 to 13.18.1 · latest laravel/framework is 13.39.0 · checked 2 Nov 2026

Yes: 3 known advisories

Yes. laravel/framework 13.18.1, the last 13.18 release, is affected by 3 known security advisories (1 critical, 1 medium, 1 low), including CVE-2026-114509, CVE-2026-114508, CVE-2026-102279. Upgrade to 13.30.0 or later to fix all of them.

Upgrade with:composer require laravel/framework:^13.30.0

Is your project affected?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Advisories affecting laravel/framework 13.18.1

  • CriticalCVE-2026-114509GHSA-f9x3-7vq9-cph623 Oct 2026

    Laravel TokenGuard authentication bypass through non-string API credentials

    Affected
    >=13.0.0 <13.29.0 · <12.68.0
    Fixed in
    12.68.0, 13.29.0
  • MediumCVE-2026-114508GHSA-5wcm-3v2w-836223 Oct 2026

    Laravel relationship inclusion can trigger unauthorized data destruction

    Affected
    >=12.45.0 <12.68.0 · >=13.0.0 <13.27.0
    Fixed in
    12.68.0, 13.27.0
  • LowCVE-2026-102279GHSA-jh5r-qr3c-85q829 Sept 2026

    Laravel: XSS in Debug Page Information

    Affected
    <12.69.0 · >=13.0.0 <13.30.0
    Fixed in
    12.69.0, 13.30.0

Which of your client projects are still on laravel/framework 13.18?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact laravel/framework version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

Other laravel/framework versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.