dbcve.org
DesignerApplication · Altium

CVE-2025-27377

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-22
Fix available
A fix is available. Upgrade to 25.2.0 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Altium Designer version 24.9.0 does not validate self-signed server certificates for cloud connections. An attacker capable of performing a man-in-the-middle (MITM) attack could exploit this issue to intercept or manipulate network traffic, potentially exposing authentication credentials or sensitive design data.

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

Altium Designer version 24.9.0 fails to validate server certificates when establishing cloud connections, allowing attackers on the network path to intercept traffic via MITM and harvest credentials or design data.

MitigationImplement network controls (VPN, SSL inspection with proper validation) for Altium Designer traffic and restrict cloud connections to trusted networks until vendor patch is available.

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
DesignerApplication
Affected:>= 24.9.0, < 25.2.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
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Check installed Altium Designer version
    Open Altium Designer and navigate to Help > About, or check the application version in installed programs list
    Affected if Version is 24.9.0 or higher but lower than 25.2.0
  2. Identify if cloud connectivity features are in use
    Check if user is logged into Altium 365 cloud service, has cloud workspace connected, or uses cloud-based design collaboration features
    Affected if Cloud account is connected or cloud workspace is active in the installation
  3. Verify SSL/TLS certificate validation behavior
    Monitor SSL/TLS handshake during Altium Designer cloud connections using a network proxy or capture tool to observe if certificate validation failures occur or certificates are accepted without proper chain validation
    Affected if Connections to Altium cloud endpoints succeed despite invalid or untrusted certificates being presented

Environment is affected if Altium Designer version is between 24.9.0 and 25.2.0 (exclusive) AND cloud connections to Altium 365 are enabled or active.

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

Implement network controls (VPN, SSL inspection with proper validation) for Altium Designer traffic and restrict cloud connections to trusted networks until vendor patch is available.

Recommended fix High confidence

Altium Designer 25.2.0 or later

  1. 1. Back up all active Altium Designer projects, libraries, and user settings to a secure location
  2. 2. Open Altium Designer and navigate to the Help menu, then check for updates or visit www.altium.com to download version 25.2.0 or later
  3. 3. Close all Altium Designer instances and any related processes
  4. 4. Uninstall the current affected version (24.9.0 through any version below 25.2.0) via Windows Control Panel > Programs and Features
  5. 5. Run the installer for the new version (25.2.0 or later) downloaded from Altium's official website
  6. 6. Follow the installation wizard prompts to complete the installation
  7. 7. Launch Altium Designer and verify cloud connection functionality works with proper certificate validation
  8. 8. Restore backed-up projects and settings as needed
Caveat Review Altium Designer 25.2.0 release notes for any new features, UI changes, or workflow modifications that may affect existing design workflows

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

Fix this in Designer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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