CVE-2024-57061
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 · uneditedAn issue in Termius Version 9.9.0 through v.9.16.0 allows a physically proximate attacker to execute arbitrary code via the insecure Electron Fuses configuration.
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 confidenceTermius versions 9.9.0 through 9.16.0 contain insecure Electron Fuses configuration, allowing a physically proximate attacker to execute arbitrary code on the affected system. Electron Fuses are build-time security flags that control runtime security behaviors; when misconfigured, they can disable critical protections like context isolation and sandboxing.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Termius version on WindowsOpen Programs and Features (appwiz.cpl), find Termius in the list, and note the version column. Alternatively, right-click the Termius desktop shortcut, select Properties, and check the Details tab for the version.Affected if Version is 9.9.0, 9.9.1, 9.10.0, 9.11.0, 9.12.0, 9.13.0, 9.14.0, 9.15.0, or 9.16.0 (any version from 9.9.0 through 9.16.0 inclusive)
-
Check installed Termius version on macOSOpen Terminal, navigate to /Applications, and run: defaults read /Applications/Termius.app/Contents/Info CFBundleShortVersionStringAffected if Version is 9.9.0, 9.9.1, 9.10.0, 9.11.0, 9.12.0, 9.13.0, 9.14.0, 9.15.0, or 9.16.0 (any version from 9.9.0 through 9.16.0 inclusive)
-
Check installed Termius version on LinuxIf installed via dpkg: dpkg -l | grep termius. If installed via snap: snap list termius. If installed via Flatpak: flatpak list | grep termius.Affected if Version is 9.9.0, 9.9.1, 9.10.0, 9.11.0, 9.12.0, 9.13.0, 9.14.0, 9.15.0, or 9.16.0 (any version from 9.9.0 through 9.16.0 inclusive)
-
Confirm version is within the affected rangeCompare the detected version number to the affected range. Versions below 9.9.0 are not affected. Versions 9.16.1 and above have the fix.Affected if The installed version falls between 9.9.0 and 9.16.0 inclusive, meaning the insecure Electron Fuses configuration is present
You are affected if Termius version is 9.9.0 through 9.16.0 inclusive, as these versions contain the misconfigured Electron Fuses that disable context isolation and sandboxing protections.
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.
From vendor dataUpdate Termius to the latest version beyond v9.16.0 which contains the corrected Electron Fuses configuration. Until patched, restrict physical access to machines running Termius and avoid using the application on shared or unattended systems.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-57061 — 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-2024-57061 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