dbcve.org
MispApplication · Misp Project

CVE-2026-44380

HIGH · 7.2 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 2.5.37 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
MISP is an open source threat intelligence and sharing platform. Prior to 2.5.37, an improper access control vulnerability in the authentication key reset functionality allowed an authenticated organization administrator to reset authentication keys belonging to site administrator accounts within the same organization. Because non-site administrators were not explicitly prevented from accessing or resetting site administrator auth keys, an attacker with organization administrator privileges could potentially obtain a newly generated auth key for a higher-privileged account and use it to escalate privileges. This vulnerability is fixed in 2.5.37.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In MISP versions prior to 2.5.37, the authentication key reset functionality lacked proper access control checks, allowing authenticated organization administrators to reset authentication keys belonging to site administrator accounts within the same organization. This improper access control enables vertical privilege escalation by permitting a lower-privileged org admin to obtain a new auth key for a higher-privileged site admin account.

MitigationUpgrade to MISP version 2.5.37 or later. Until then, restrict organization administrator privileges to trusted personnel and monitor authentication key changes for suspicious activity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MispApplication
Affected:< 2.5.37

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed MISP version
    Access the MISP administration interface and navigate to Server Settings > Diagnostics, or run 'git log' in the MISP installation directory to check the current version. Alternatively, check the version displayed in the footer of any MISP page.
    Affected if The installed version is lower than 2.5.37 (e.g., 2.5.36, 2.5.35, etc.)
  2. Identify organization administrator accounts
    Navigate to Administration > Users in the MISP interface and review the 'Role' column for users assigned the 'Org Administrator' role. Count how many org admin accounts exist.
    Affected if Multiple organization administrator accounts exist, especially if they belong to the same organisation as site administrators
  3. Review authentication key audit logs
    Navigate to the MISP audit logs (Administration > Audit) or check the logs directory for entries related to 'authkey' or 'reset'. Look for authentication key reset or regeneration events.
    Affected if Any authentication key reset events are present for site administrator accounts that were not initiated by the site administrator themselves
  4. Check for unauthorized auth key changes
    Compare current authentication keys for site administrator accounts against known previous values, or review the 'last used' timestamp in Administration > Users for site admin accounts.
    Affected if Authentication keys for site administrator accounts have been regenerated or show recent usage that does not correspond to the actual site admin activity

A user is affected if their MISP installation is version 2.5.36 or earlier AND they have organization administrator accounts that could have reset site administrator authentication keys.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.5.37 or later
Fixed in 2.5.37
Interim mitigation

Upgrade to MISP version 2.5.37 or later. Until then, restrict organization administrator privileges to trusted personnel and monitor authentication key changes for suspicious activity.

Recommended fix High confidence

MISP 2.5.37

  1. Backup your current MISP installation and database before upgrading
  2. Download MISP version 2.5.37 from the official GitHub repository (github.com/MISP/MISP)
  3. Extract the new version to your MISP installation directory
  4. Run the database upgrade script if included: cd app && Console/cake Admin updateDatabase
  5. Clear MISP cache: cd app && Console/cake Admin cacheClearAll
  6. Verify the upgrade was successful by logging in and checking the version number under the administration menu
Caveat Review release notes for any configuration changes required between your current version and 2.5.37

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Misp Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44380 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44380 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data