dbcve.org
QumagieApplication · Qnap

CVE-2026-26236

HIGH · 7.5 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 2.9.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
A missing authorization vulnerability has been reported to affect QuMagie. The remote attackers can then exploit the vulnerability to access unauthorized data or perform unauthorized actions. We have already fixed the vulnerability in the following version: QuMagie 2.9.0 and later

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

This is a missing authorization (broken access control) vulnerability in QuMagie, QNAP's AI-powered photo management application. Remote attackers can exploit the lack of proper authorization checks to access data or perform actions beyond their intended permissions without proper authentication validation.

MitigationUpdate QuMagie to version 2.9.0 or later to obtain the vendor-provided authorization fix. If unable to update immediately, restrict network exposure of the QuMagie service to trusted users.

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
QumagieApplication
Affected:< 2.9.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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Confirm QuMagie is installed on the QNAP device
    Log into QTS admin interface, open App Center, and look for QuMagie in the installed applications list. Alternatively, use CLI: run 'getcfg QuMagie' or check /share/CACHEDEV1_DATA/.qpkg/QuMagie directory exists.
    Affected if QuMagie is not found in installed applications - the system is not affected because the vulnerable software is not present.
  2. Identify the installed QuMagie version
    In QTS: go to App Center, find QuMagie, and click on it to view version information. Or via CLI: check the .qpkg/QuMagie directory for a version file, or run 'qpkg -e QuMagie' to get package details.
    Affected if The displayed version number is lower than 2.9.0 (for example, 2.8.x, 2.7.x, etc.) - the version is vulnerable.
  3. Verify the exact version against vulnerable range
    Compare the installed version to the affected range: any version prior to 2.9.0 is vulnerable. Note that version 2.9.0 itself and later versions are not affected.
    Affected if Installed version is 2.8.0, 2.7.5, or any version string starting with 2.x where x is less than 9 - the system is affected by the missing authorization flaw.
  4. Determine network accessibility of QuMagie interface
    Check if QuMagie web portal is accessible over network by attempting to access https://[QNAP-IP]:[port]/qumagie or checking QTS > Control Panel > Applications > QuMagie for web service binding settings.
    Affected if QuMagie web interface is exposed to untrusted networks without proper firewall restrictions - the authorization bypass can be exploited remotely.

You are affected if QuMagie is installed and the installed version is any release prior to 2.9.0, and the service is network-accessible.

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

Update QuMagie to version 2.9.0 or later to obtain the vendor-provided authorization fix. If unable to update immediately, restrict network exposure of the QuMagie service to trusted users.

Recommended fix High confidence

QuMagie 2.9.0

  1. 1. Check the current installed version of QuMagie on the QNAP device
  2. 2. Ensure all data backups are up to date before proceeding with the upgrade
  3. 3. Access the QNAP Admin Console and navigate to the App Center or QuMagie application management
  4. 4. Update QuMagie to version 2.9.0 or later
  5. 5. Verify the upgrade was successful by checking the installed version number
  6. 6. Test that QuMagie functionality is working normally after the update

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

Fix this in Qumagie Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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