dbcve.org
Quartus PrimeApplication · Intel

CVE-2025-14614

MEDIUM · 6.7 CVSS v3.1 Published 2026-01-07
Fix available
A fix is available. Upgrade to 25.1 or later.
See remediation →
67/100
Remediation priority · Elevated

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
Insecure Temporary File vulnerability in Altera Quartus Prime Standard  Installer (SFX) on Windows, Altera Quartus Prime Lite  Installer (SFX) on Windows allows Explore for Predictable Temporary File Names.This issue affects Quartus Prime Standard: from 23.1 through 24.1; Quartus Prime Lite: from 23.1 through 24.1.

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 confidence

Insecure temporary file vulnerability in Altera Quartus Prime Standard and Lite SFX installers on Windows allows attackers to exploit predictable temporary file names. The installer creates temporary files in a location that can be explored/written to by unprivileged users, potentially enabling privilege escalation or code execution when the installer runs with elevated privileges.

MitigationUpdate Quartus Prime to version 24.2 or later when available, or avoid running the installer in untrusted multi-user environments until the vendor patch is released.

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
Quartus PrimeApplication
Affected:>= 23.1, < 25.1

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

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/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. Check if Quartus Prime is installed
    Open Windows Registry and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Intel\QuartusPrime (or check C:\intelquartus for installation directory). Look for version information in the registry or check the version.txt file in the installation directory.
    Affected if Quartus Prime is found on the system
  2. Determine installed version number
    Read the version from the registry key or inspect the version.txt file in the Quartus Prime installation folder. The version format is typically XX.X where XX.X represents the major.minor version (e.g., 23.1, 23.2, 24.1).
    Affected if The version number cannot be determined or is not visible
  3. Compare version against affected range
    If a version is identified, compare it to the affected range: versions 23.1 through 24.3 (any version >= 23.1 and < 25.1) are affected. Versions 25.1 and later, or versions before 23.1, are not in the affected range.
    Affected if The installed version is 23.1, 23.2, 23.3, 23.4, 24.1, 24.2, or 24.3 (any version >= 23.1 but less than 25.1)
  4. Inspect temporary directories for installer artifacts
    Examine the Windows temporary folder (%TEMP% or C:\Users\<username>\AppData\Local\Temp) and any Quartus-related temp directories for .tmp files, extraction logs, or SFX installer remnants that may indicate recent installer execution.
    Affected if SFX installer was recently run and left predictable temporary files in a world-writable location

The system is affected if Quartus Prime version 23.1 through 24.3 is installed and the SFX installer was executed in a multi-user Windows environment where unprivileged users can access the temporary file location.

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.1 or later
Fixed in 25.1
Interim mitigation

Update Quartus Prime to version 24.2 or later when available, or avoid running the installer in untrusted multi-user environments until the vendor patch is released.

Recommended fix High confidence

Quartus Prime 25.1 or later (Standard or Lite depending on your edition)

  1. 1. Download Quartus Prime version 25.1 or later from the official Altera (Intel) website: www.altera.com
  2. 2. Verify the checksum of the downloaded installer to ensure integrity
  3. 3. Close all running instances of Quartus Prime and related tools
  4. 4. Run the Quartus Prime 25.1 installer with administrator privileges
  5. 5. Follow the installation wizard prompts to complete the upgrade
  6. 6. After installation, verify the version by checking Help > About Quartus Prime in the software
Caveat Major version upgrades may include workflow changes; review the Quartus Prime 25.1 release notes for any new features, deprecated tools, or migration considerations before upgrading

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

Fix this in Quartus Prime Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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