CVE-2026-14542 · Infrastructure
NO FIX YET
The VAPIX SIP configuration API on Axis devices does not validate input well enough. An attacker who already holds an admin-privileged service account can use it to escalate privileges.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Affected systems are Axis network devices that expose the VAPIX SIP configuration API. Exploitation requires an admin-privileged service account first, so exposure depends on who holds such credentials. The sources do not name affected firmware versions or say how to confirm that SIP configuration is enabled.
Not affected if no-admin-service-accounts, sip-not-configured
Who cares axis, network-cameras, sip, vapix
Unknown from the sources.
No fix yet, per the sources.
The VAPIX SIP configuration API lacked sufficient input validation, which could potentially lead to privilege escalation. This flaw can only be exploited after authenticating with an admin-privileged service account.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.