Is jackalope/jackalope-doctrine-dbal 1.7 vulnerable?

Composer · 7 releases from 1.7.0 to 1.7.6 · latest jackalope/jackalope-doctrine-dbal is 2.0.3 · checked 18 Nov 2026

No known advisories in the last release

jackalope/jackalope-doctrine-dbal 1.7.6, the last 1.7 release, has no known advisories. 1 advisory affects earlier 1.7.x releases, so update to 1.7.6.

Update within 1.7:composer require jackalope/jackalope-doctrine-dbal:^1.7.6

Is your project on an affected jackalope/jackalope-doctrine-dbal?

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

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 1.7.x, affecting earlier releases

  • HighCVE-2021-43822GHSA-ph98-v78f-jqrm14 Dec 2021

    SQL injection in jackalope/jackalope-doctrine-dbal

    Affected
    <1.7.4
    Fixed in
    1.7.4

Every jackalope/jackalope-doctrine-dbal 1.7.x release

Affected: 1.7.0 to 1.7.3. 1.7.4 and later are not affected. Latest jackalope/jackalope-doctrine-dbal: 2.0.3.

VersionKnown advisories
jackalope/jackalope-doctrine-dbal 1.7.6None
jackalope/jackalope-doctrine-dbal 1.7.5None
jackalope/jackalope-doctrine-dbal 1.7.4None
jackalope/jackalope-doctrine-dbal 1.7.3CVE-2021-43822
jackalope/jackalope-doctrine-dbal 1.7.2CVE-2021-43822
jackalope/jackalope-doctrine-dbal 1.7.1CVE-2021-43822
jackalope/jackalope-doctrine-dbal 1.7.0CVE-2021-43822

Which of your client projects are still on jackalope/jackalope-doctrine-dbal 1.7?

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

Other jackalope/jackalope-doctrine-dbal 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.