dbcve.org
Quartus PrimeApplication · Intel

CVE-2025-14612

MEDIUM · 6.7 CVSS v3.1 Published 2026-01-07
Fix available
A fix is available. Upgrade to 25.3 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 Pro  Installer (SFX) on Windows allows : Use of Predictable File Names.This issue affects Quartus Prime Pro: from 24.1 through 25.1.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

The Altera Quartus Prime Pro Installer (SFX) on Windows uses predictable file names when creating temporary files during extraction and installation. This predictability could allow a local attacker to potentially replace or manipulate temporary files before they are used by the installer, leading to potential code execution or file overwrite attacks.

MitigationApply the vendor patch when available. In the interim, ensure the installer runs in a secure, controlled environment with restricted permissions to the temporary directory and avoid running the installer from shared/network locations.

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:>= 24.1, < 25.3

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 installed Intel Quartus Prime version
    Open Quartus Prime and navigate to Help > About, or check the installation directory for a version file. On Windows, also check Programs and Features in Control Panel for the installed version.
    Affected if The installed version is >= 24.1 and < 25.3
  2. Locate the Quartus Prime installer executable
    Search for QuartusPrimeSetup*.exe or similar installer files in download folders, installation media, or software repositories.
    Affected if The installer file version (if obtainable via right-click > Properties > Details) is < 25.3 and you ran this installer on this system
  3. Check for residual temporary installation files
    Examine the system temporary directory (%TEMP% or %TMP%) for any Quartus-related folders or files with predictable sequential names (such as QuartusSetup_001, QuartusSetup_002).
    Affected if Temporary files with sequential/predictable naming patterns from Quartus installation exist in the temp directory
  4. Review installation logs for predictable file operations
    If installation logs exist (check the Quartus installation directory or %TEMP% for log files), search for mentions of temp file creation with sequential or timestamp-based names.
    Affected if Logs show temp files being created with predictable sequential or timestamp-based names rather than random GUIDs

A user is affected if they used an Intel Quartus Prime installer version 24.1 through 25.2 to install the software on this Windows system, as the installer used predictable temporary file names during extraction.

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.3 or later
Fixed in 25.3
Interim mitigation

Apply the vendor patch when available. In the interim, ensure the installer runs in a secure, controlled environment with restricted permissions to the temporary directory and avoid running the installer from shared/network locations.

Recommended fix Moderate confidence

Quartus Prime Pro 25.3

  1. 1. Download Quartus Prime Pro version 25.3 or later from the official Intel/Altera website (www.altera.com)
  2. 2. Ensure you have administrator privileges on your Windows system
  3. 3. If you have Quartus Prime currently running, close the application completely
  4. 4. Run the Quartus Prime Pro 25.3 installer (SFX) on Windows
  5. 5. Follow the installation wizard prompts to complete the installation
  6. 6. After installation, verify the installed version by checking Help > About Quartus Prime in the software

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

Fix this in Quartus Prime Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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