Is NHibernate 3.1 vulnerable?

NuGet · 1 release from 3.1.0.4000 to 3.1.0.4000 · latest NHibernate is 5.7.1 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. NHibernate 3.1.0.4000, the last 3.1 release, is affected by 1 known security advisory (1 high), including CVE-2024-39677. Upgrade to 5.4.9 or later to fix all of them.

Upgrade with:dotnet add package NHibernate --version 5.4.9

Is your project on an affected NHibernate?

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

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

Advisories affecting NHibernate 3.1.0.4000

  • HighCVE-2024-39677GHSA-fg4q-ccq8-3r5q8 Jul 2024

    NHibernate SQL injection vulnerability in discriminator mappings, static fields referenced in HQL, and some utilities

    Affected
    <5.4.9 · >=5.5.0 <5.5.2
    Fixed in
    5.4.9, 5.5.2

Which of your client projects are still on NHibernate 3.1?

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

Other NHibernate versions

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