dbcve.org
Biodose\/nmisApplication · Mirion

CVE-2025-64778

HIGH · 7.8 CVSS v3.1 Published 2025-12-02
Fix available
A fix is available. Upgrade to 23.0 or later.
See remediation →
80/100
Remediation priority · High
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
NMIS/BioDose software V22.02 and previous versions contain executable binaries with plain text hard-coded passwords. These hard-coded passwords could allow unauthorized access to both the application and database.

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

NMIS/BioDose software V22.02 and previous versions contain executable binaries with plain text hard-coded passwords embedded directly in the code. These hardcoded credentials provide direct authentication access to both the application layer and underlying database without requiring proper credential management.

MitigationRemove all hardcoded passwords from binaries and replace with secure credential storage mechanisms (environment variables, secrets vault, or encrypted configuration), then rotate all exposed credentials and update affected binaries.

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
Biodose\/nmisApplication
Affected:< 23.0

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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. Identify Mirion Biodose or NMIS installation
    Locate the installed Biodose or NMIS software on the system. Check common installation directories or use system package management tools to find the application.
    Affected if The software is installed and is Mirion Biodose or NMIS
  2. Determine installed software version
    Run the version command for the Biodose/NMIS application, check the About dialog, or inspect version information in installation files or configuration.
    Affected if The version is V22.02 or any version prior to 23.0 (i.e., version < 23.0)
  3. Locate application executable binaries
    Find the main executable files for the Biodose or NMIS application in the installation directory.
    Affected if Executable binaries exist for the affected product
  4. Examine binaries for embedded plain text passwords
    Use string extraction tools (such as 'strings' on Linux or equivalent) on the executable binaries to search for patterns resembling passwords, keys, or credential-like data embedded in plain text.
    Affected if Plain text passwords or credentials are found embedded within the binary code
  5. Verify database and application authentication configuration
    Inspect application configuration files, database connection settings, or authentication modules to confirm whether hardcoded credentials are being used for access.
    Affected if Authentication relies on hardcoded credentials embedded in binaries rather than secure credential storage

You are affected if Mirion Biodose or NMIS software is installed with a version lower than 23.0 and uses executable binaries containing hardcoded plain text passwords for application or database authentication.

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 23.0 or later
Fixed in 23.0
Interim mitigation

Remove all hardcoded passwords from binaries and replace with secure credential storage mechanisms (environment variables, secrets vault, or encrypted configuration), then rotate all exposed credentials and update affected binaries.

Recommended fix Moderate confidence

Version 23.0 or later

  1. Backup all application data, configurations, and database before proceeding with the upgrade
  2. Upgrade NMIS/BioDose from any version < 23.0 to version 23.0 or later
  3. After upgrade, verify that the hard-coded credentials have been removed from all executable binaries
  4. Change any default passwords that may have been used during the initial setup after upgrading
  5. Verify that unauthorized access to the application and database is no longer possible with the old credentials
Caveat Review release notes for version 23.0 to check for any configuration or compatibility changes that may affect your deployment

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

Fix this in Biodose\/nmis Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64778 — 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-2025-64778 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