CVE-2026-42929
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 · uneditedDanelec MacGregor Voyage Data Recorder includes default accounts with hard-coded credentials.
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 · moderate confidenceDanelec MacGregor Voyage Data Recorder (VDR) systems contain hard-coded default credentials embedded in firmware. This allows authenticated attackers to access the VDR system, potentially compromising critical maritime navigation and communication data recording functions used for accident investigation and safety compliance.
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< 5.250CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the VDR device modelLocate the Voyage Data Recorder unit and check the model labeling, or query the system for device identification information. Look for 'Macgregor Interschalt Vdr G4e' branding or model strings.Affected if The system is NOT a Macgregor Interschalt Vdr G4e model - this vulnerability only affects that specific device.
-
Check the installed firmware versionAccess the VDR system management interface or use the appropriate command/utility to retrieve the firmware version. Compare it against the affected range of versions below 5.250.Affected if The firmware version is 5.250 or higher - versions at and above 5.250 are not affected by this CVE.
-
Locate credential configurationAccess the VDR administrative interface or examine the system configuration files where user accounts and passwords are stored. Look for accounts that may use default or hard-coded credentials.Affected if Default credentials are still active or have not been changed from manufacturer defaults - this is the condition that makes the vulnerability exploitable.
-
Verify network accessibility of management interfaceDetermine if the VDR management interface is accessible from the network. Check firewall rules, network segmentation, and interface binding configurations.Affected if The VDR management interface is exposed to an untrusted network without proper access controls, increasing exploitation risk.
The environment is affected if it runs a Macgregor Interschalt Vdr G4e with firmware version below 5.250 and the default credentials remain unchanged or accessible from the network.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.250
Immediately change all default credentials on affected VDR systems, disable unused default accounts, and contact Danelec MacGregor for patched firmware or guidance on credential management. Restrict network access to VDR management interfaces.
Interschalt Vdr G4e Firmware version 5.250 or later
- Identify all Interschalt Vdr G4e devices on the network running firmware versions prior to 5.250
- Contact Danelec MacGregor to obtain the official firmware version 5.250 or later that addresses the hard-coded credentials vulnerability
- Download the firmware update from an official Danelec MacGregor source (www.danelec.com) or through authorized support channels
- Review the firmware release notes to confirm the fix addresses CWE-798 hard-coded credentials (CVE-2026-42929)
- Schedule a maintenance window for the firmware update following vessel operational requirements
- Apply the firmware update to all affected Vdr G4e devices following the manufacturer's documented upgrade procedure
- After upgrading, verify that default hard-coded accounts have been removed or replaced with unique, changeable credentials
- Change any default passwords immediately after upgrade following secure password practices
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42929 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-42929 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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