CVE-2025-6298
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 · uneditedACAP applications can gain elevated privileges due to improper input validation, potentially leading to privilege escalation. This vulnerability can only be exploited if the Axis device is configured to allow the installation of unsigned ACAP applications, and if an attacker convinces the victim to install a malicious ACAP application.
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 confidenceThis is a privilege escalation vulnerability in Axis network devices where ACAP (Axis Application Platform) applications can gain elevated privileges due to improper input validation. Exploitation requires the device to be configured to allow unsigned ACAP applications and the victim to be tricked into installing a malicious ACAP application.
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< 12.6.28CVSS 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
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 Axis OS versionAccess the device web interface and navigate to System > About or use the CLI command 'show version' via SSH to retrieve the installed Axis OS version numberAffected if The installed version is lower than 12.6.28 (e.g., 12.5.x, 11.x, etc.)
-
Check ACAP application signed application settingLog into the Axis device web interface and navigate to Apps > App Categories > Settings, or check the device configuration for an option controlling unsigned/third-party ACAP application installationAffected if The setting allows installation of unsigned or unverified ACAP applications (the option to install non-signed apps is enabled)
-
Identify installed ACAP applicationsAccess the device web interface under Apps or Applications menu to list all installed ACAP applications, noting their names, publishers, and installation datesAffected if Any unknown, recently installed, or untrusted ACAP applications are present on the device
A device is affected if it runs Axis OS version below 12.6.28 AND has the configuration that permits unsigned ACAP applications to be installed.
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.
dbcve · scoped12.6.28
Disable the configuration that allows installation of unsigned ACAP applications and only install ACAP applications from trusted, verified sources. Review and harden Axis device security settings.
Axis OS 12.6.28
- Log in to the Axis device web interface or use AXIS Device Manager to check the current OS version
- Back up the device configuration before proceeding with the upgrade
- Navigate to the firmware update or system upgrade section in the device management interface
- Upgrade the device firmware to Axis OS version 12.6.28 or later
- Verify the upgrade was successful by confirming the new OS version in the device interface
- Ensure the device is properly functioning after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6298 — 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-2025-6298 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