- Top reward
- $50,000
- Top severity paid
- Critical
- Assets in scope
- 1
- Public CVEs
- 60
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $50,000
- for critical bugs, from $500.
- Report on Bugcrowd
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What Bugcrowd lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$40,000 |
| High |
|
$10,000 |
| Medium |
|
$2,000 |
| Low |
|
$500 |
Earlier reward tables (1)
- 11 Nov 2026 to 11 Nov 2026: Critical up to $40,000
Scope
1 asset you may test.
Hardware and IoT 1
- AXIS OS
Rules
What the policy asks of you, and the bug types it won't reward, quoted from AXIS OS (via Bugcrowd)'s policy.
While testing
-
Do not change the root password or factory default the device.
-
Axis will validate all submissions against the latest AXIS OS 13 device software available on axis.com .
Not accepted
-
Vulnerabilities that affect only earlier software versions are out of scope and are not eligible for a bounty.
-
Vulnerabilities requiring local system access, including system-level issues such as D-Bus authorization bypasses, are out of scope
-
Vulnerabilities caused by user configurations that could be prevented by following the Axis OS Hardening Guide
-
User uploaded created content or applications, for instance ACAPs that can be uploaded and run on Axis devices.
-
Social-engineered attacks such as Cross-Site Request Forgery (CSRF) or Cross-Site scripting (XSS) vulnerabilities
-
Vulnerabilities in Axis-branded pre-installed or uploaded applications (ACAPs)
-
Vulnerabilities listed by 3rd party network security scanners
-
Any DoS type attack
-
Errors in API documentation.
-
GUI flaws/errors that can be corrected through the VAPIX/Onvif API.
-
Attacks that depends on Man-in-the-Middle (MitM) conditions.
-
Functionality restricted by feature flags .
Summarised with AI from the program policy on Bugcrowd, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 1 hour ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
| CVE | Summary | Severity | Published |
|---|---|---|---|
| CVE-2026-0804 | An ACAP configuration file lacked sufficient input validation, which could allow a path traversal attack leading to potential 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. | Medium 6.7 | 12 May 2026 |
| CVE-2026-1185 | A configuration file on the local file system had improper input validation which could allow code execution and potentially lead to privilege escalation. This vulnerability can only be exploited if an attacker can log in to the Axis device using SSH. | Medium 5.4 | 12 May 2026 |
| CVE-2026-0541 | ACAP applications can gain elevated privileges due to improper input validation during the installation process, 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. | Medium 6.7 | 12 May 2026 |
| CVE-2026-0802 | An ACAP configuration file lacked sufficient input validation, which could allow command injection and potentially lead 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. | Medium 6.0 | 12 May 2026 |
| CVE-2025-12063 | An insecure direct object reference allowed a non-admin user to modify or remove certain data objects without having the appropriate permissions. | Medium 5.7 | 10 Feb 2026 |
| CVE-2025-13064 | A server-side injection was possible for a malicious admin to manipulate the application to include a malicious script which is executed by the server. This attack is only possible if the admin uses a client that have been tampered with. | Medium 4.5 | 10 Feb 2026 |
| CVE-2025-11547 | AXIS Camera Station Pro contained a flaw to perform a privilege escalation attack on the server as a non-admin user. | High 7.8 | 10 Feb 2026 |
| CVE-2025-12757 | An AXIS Camera Station Pro feature can be exploited in a way that allows a non-admin user to view information they are not permitted to. | Medium 4.6 | 10 Feb 2026 |
| CVE-2025-11142 | The VAPIX API mediaclip.cgi that did not have a sufficient input validation allowing for a possible remote code execution. This flaw can only be exploited after authenticating with an operator- or administrator- privileged service account. | High 7.1 | 10 Feb 2026 |
| CVE-2025-8108 | An ACAP configuration file has improper permissions and lacks input validation, which could potentially lead 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. | Medium 6.7 | 11 Nov 2025 |
| CVE-2025-6779 | An ACAP configuration file has improper permissions, which could allow command injection and potentially lead 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. | Medium 6.7 | 11 Nov 2025 |
| CVE-2025-5452 | A malicious ACAP application can gain access to admin-level service account credentials used by legitimate ACAP applications, leading to potential privilege escalation of the malicious ACAP application. 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 ACA | Medium 6.6 | 11 Nov 2025 |
| CVE-2025-6298 | ACAP 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. | Medium 6.7 | 11 Nov 2025 |
| CVE-2025-5718 | The ACAP Application framework could allow privilege escalation through a symlink attack. 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. | Medium 6.8 | 11 Nov 2025 |
| CVE-2025-5454 | An ACAP configuration file lacked sufficient input validation, which could allow a path traversal attack leading to potential 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. | Medium 6.4 | 11 Nov 2025 |
| CVE-2025-4645 | An ACAP configuration file lacked sufficient input validation, which could allow for arbitrary code execution. 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. | Medium 6.7 | 11 Nov 2025 |
| CVE-2025-30027 | An ACAP configuration file lacked sufficient input validation, which could allow for arbitrary code execution. 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. | Medium 6.7 | 12 Aug 2025 |
| CVE-2025-3892 | ACAP applications can be executed with elevated privileges, 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. | Medium 6.7 | 12 Aug 2025 |
| CVE-2025-7622 | During an internal security assessment, a Server-Side Request Forgery (SSRF) vulnerability that allowed an authenticated attacker to access internal resources on the server was discovered. | Medium 5.1 | 12 Aug 2025 |
| CVE-2025-30024 | The communication protocol used between client and server had a flaw that could be leveraged to execute a man in the middle attack. | Medium 6.8 | 11 Jul 2025 |
| CVE-2025-30026 | The AXIS Camera Station Server had a flaw that allowed to bypass authentication that is normally required. | Medium 5.3 | 11 Jul 2025 |
| CVE-2025-30025 | The communication protocol used between the server process and the service control had a flaw that could lead to a local privilege escalation. | Medium 4.8 | 11 Jul 2025 |
| CVE-2025-30023 | The communication protocol used between client and server had a flaw that could lead to an authenticated user performing a remote code execution attack. | Critical 9.0 | 11 Jul 2025 |
| CVE-2025-0358 | During an annual penetration test conducted on behalf of Axis Communication, Truesec discovered a flaw in the VAPIX Device Configuration framework that allowed a privilege escalation, enabling a lower-privileged user to gain administrator privileges. | High 8.8 | 2 Jun 2025 |
| CVE-2025-0324 | The VAPIX Device Configuration framework allowed a privilege escalation, enabling a lower-privileged user to gain administrator privileges. | Critical 9.4 | 2 Jun 2025 |
| CVE-2025-1056 | Gee-netics, member of AXIS Camera Station Pro Bug Bounty Program, has identified an issue with a specific file that the server is using. A non-admin user can modify this file to either create files or change the content of files in an admin-protected location. Axis has released a patched version for the highlighted flaw. Please refer to the Axis security advisory for more information and solution. | Medium 6.1 | 23 Apr 2025 |
| CVE-2025-0926 | Gee-netics, member of AXIS Camera Station Pro Bug Bounty Program, has found that it is possible for a non-admin user to remove system files causing a boot loop by redirecting a file deletion when recording video. Axis has released a patched version for the highlighted flaw. Please refer to the Axis security advisory for more information and solution. | Medium 5.9 | 23 Apr 2025 |
| CVE-2025-0361 | During an annual penetration test conducted on behalf of Axis Communications, Truesec discovered a flaw in the VAPIX Device Configuration framework that allowed for unauthenticated username enumeration through the VAPIX Device Configuration SSH Management API. | Medium 4.3 | 8 Apr 2025 |
| CVE-2024-47261 | 51l3nc3, a member of the AXIS OS Bug Bounty Program, has found that the VAPIX API uploadoverlayimage.cgi did not have sufficient input validation to allow an attacker to upload files to block access to create image overlays in the web interface of the Axis device. | Medium 4.3 | 8 Apr 2025 |
| CVE-2025-0360 | During an annual penetration test conducted on behalf of Axis Communication, Truesec discovered a flaw in the VAPIX Device Configuration framework that could lead to an incorrect user privilege level in the VAPIX service account D-Bus API. | High 7.8 | 4 Mar 2025 |
| CVE-2025-0359 | During an annual penetration test conducted on behalf of Axis Communication, Truesec discovered a flaw in the ACAP Application framework that allowed applications to access restricted D-Bus methods within the framework. Axis has released patched AXIS OS versions for the highlighted flaw. Please refer to the Axis security advisory for more information and solution. | High 8.5 | 4 Mar 2025 |
| CVE-2024-47259 | Girishunawane, member of the AXIS OS Bug Bounty Program, has found that the VAPIX API dynamicoverlay.cgi did not have a sufficient input validation allowing for a possible command injection leading to being able to transfer files to the Axis device with the purpose to exhaust system resources. Axis has released patched AXIS OS versions for the highlighted flaw. Please refer to the Axis security ad | Low 3.5 | 4 Mar 2025 |
| CVE-2024-7696 | Seth Fogie, member of AXIS Camera Station Pro Bug Bounty Program, has found that it is possible for an authenticated malicious client to tamper with audit log creation in AXIS Camera Station, or perform a Denial-of-Service attack on the AXIS Camera Station server using maliciously crafted audit log entries. Axis has released a patched version for the highlighted flaw. Please refer to the Axis secu | Medium 6.3 | 7 Jan 2025 |
| CVE-2024-8160 | Erik de Jong, member of the AXIS OS Bug Bounty Program, has found that the VAPIX API ftptest.cgi did not have a sufficient input validation allowing for a possible command injection leading to being able to transfer files from/to the Axis device. This flaw can only be exploited after authenticating with an administrator-privileged service account. Axis has released patched AXIS OS versions for the | Low 3.8 | 26 Nov 2024 |
| CVE-2024-6979 | Amin Aliakbari, member of the AXIS OS Bug Bounty Program, has found a broken access control which would lead to less-privileged operator- and/or viewer accounts having more privileges than designed. The risk of exploitation is very low as it requires complex steps to execute, including knowing of account passwords and social engineering attacks in tricking the administrator to perform specific con | Medium 6.8 | 10 Sep 2024 |
| CVE-2024-0055 | Sandro Poppi, member of the AXIS OS Bug Bounty Program, has found that the VAPIX APIs mediaclip.cgi and playclip.cgi was vulnerable for file globbing which could lead to a resource exhaustion attack. Axis has released patched AXIS OS versions for the highlighted flaw. Please refer to the Axis security advisory for more information and solution. | Medium 6.5 | 19 Mar 2024 |
| CVE-2023-5677 | Brandon Rothel from QED Secure Solutions and Sam Hanson of Dragos have found that the VAPIX API tcptest.cgi did not have a sufficient input validation allowing for a possible remote code execution. This flaw can only be exploited after authenticating with an operator- or administrator-privileged service account. The impact of exploiting this vulnerability is lower with operator-privileges compared | Medium 6.3 | 5 Feb 2024 |
| CVE-2023-5800 | Vintage, member of the AXIS OS Bug Bounty Program, has found that the VAPIX API create_overlay.cgi did not have a sufficient input validation allowing for a possible remote code execution. This flaw can only be exploited after authenticating with an operator- or administrator-privileged service account. Axis has released patched AXIS OS versions for the highlighted flaw. Please refer to the Axis s | Medium 5.4 | 5 Feb 2024 |
| CVE-2023-5553 | During internal Axis Security Development Model (ASDM) threat-modelling, a flaw was found in the protection for device tampering (commonly known as Secure Boot) in AXIS OS making it vulnerable to a sophisticated attack to bypass this protection. To Axis' knowledge, there are no known exploits of the vulnerability at this time. Axis has released patched AXIS OS versions for the highlighted flaw. Pl | High 7.6 | 21 Nov 2023 |
| CVE-2023-21418 | Sandro Poppi, member of the AXIS OS Bug Bounty Program, has found that the VAPIX API irissetup.cgi was vulnerable to path traversal attacks that allows for file deletion. This flaw can only be exploited after authenticating with an operator- or administrator-privileged service account. The impact of exploiting this vulnerability is lower with operator service accounts and limited to non-system fil | High 7.1 | 21 Nov 2023 |
| CVE-2023-21417 | Sandro Poppi, member of the AXIS OS Bug Bounty Program, has found that the VAPIX API manageoverlayimage.cgi was vulnerable to path traversal attacks that allows for file/folder deletion. This flaw can only be exploited after authenticating with an operator- or administrator- privileged service account. The impact of exploiting this vulnerability is lower with operator service accounts and limited | High 7.1 | 21 Nov 2023 |
| CVE-2023-21416 | Sandro Poppi, member of the AXIS OS Bug Bounty Program, has found that the VAPIX API dynamicoverlay.cgi was vulnerable to a Denial-of-Service attack allowing for an attacker to block access to the overlay configuration page in the web interface of the Axis device. This flaw can only be exploited after authenticating with an operator- or administrator-privileged service account however the impact i | High 7.1 | 21 Nov 2023 |
| CVE-2023-21414 | NCC Group has found a flaw during the annual internal penetration test ordered by Axis Communications. The protection for device tampering (commonly known as Secure Boot) contains a flaw which provides an opportunity for a sophisticated attack to bypass this protection. Axis has released patched AXIS OS versions for the highlighted flaw. Please refer to the Axis security advisory for more informat | High 7.1 | 16 Oct 2023 |
| CVE-2023-21415 | Sandro Poppi, member of the AXIS OS Bug Bounty Program, has found that the VAPIX API overlay_del.cgi is vulnerable to path traversal attacks that allows for file deletion. This flaw can only be exploited after authenticating with an operator- or administrator-privileged service account. Axis has released patched AXIS OS versions for the highlighted flaw. Please refer to the Axis security advisory | Medium 6.5 | 16 Oct 2023 |
| CVE-2023-21413 | GoSecure on behalf of Genetec Inc. has found a flaw that allows for a remote code execution during the installation of ACAP applications on the Axis device. The application handling service in AXIS OS was vulnerable to command injection allowing an attacker to run arbitrary code. Axis has released patched AXIS OS versions for the highlighted flaw. Please refer to the Axis security advisory for mor | Critical 9.1 | 16 Oct 2023 |
| CVE-2023-21410 | User provided input is not sanitized on the AXIS License Plate Verifier specific “api.cgi” allowing for arbitrary code execution. | High 7.2 | 3 Aug 2023 |
| CVE-2023-21408 | Due to insufficient file permissions, unprivileged users could gain access to unencrypted user credentials that are used in the integration interface towards 3rd party systems. | High 8.4 | 3 Aug 2023 |
| CVE-2023-21407 | A broken access control was found allowing for privileged escalation of the operator account to gain administrator privileges. | High 8.8 | 3 Aug 2023 |
| CVE-2023-21412 | User provided input is not sanitized on the AXIS License Plate Verifier specific “search.cgi” allowing for SQL injections. | High 7.2 | 3 Aug 2023 |
| CVE-2023-21411 | User provided input is not sanitized in the “Settings > Access Control” configuration interface allowing for arbitrary code execution. | High 7.2 | 3 Aug 2023 |
| CVE-2023-21409 | Due to insufficient file permissions, unprivileged users could gain access to unencrypted administrator credentials allowing the configuration of the application. | High 8.4 | 3 Aug 2023 |
| CVE-2023-21406 | Ariel Harush and Roy Hodir from OTORIO have found a flaw in the AXIS A1001 when communicating over OSDP. A heap-based buffer overflow was found in the pacsiod process which is handling the OSDP communication allowing to write outside of the allocated buffer. By appending invalid data to an OSDP message it was possible to write data beyond the heap allocated buffer. The data written outside the buf | High 7.1 | 25 Jul 2023 |
| CVE-2023-21405 | Knud from Fraktal.fi has found a flaw in some Axis Network Door Controllers and Axis Network Intercoms when communicating over OSDP, highlighting that the OSDP message parser crashes the pacsiod process, causing a temporary unavailability of the door-controlling functionalities meaning that doors cannot be opened or closed. No sensitive or customer data can be extracted as the Axis device is not f | Medium 6.5 | 25 Jul 2023 |
| CVE-2023-21404 | AXIS OS 11.0.X - 11.3.x use a static RSA key in legacy LUA-components to protect Axis-specific source code. The static RSA key is not used in any other secure communication nor can it be used to compromise the device or any customer data. | Medium 5.3 | 8 May 2023 |
| CVE-2023-22984 | A Vulnerability was discovered in Axis 207W network camera. There is a reflected XSS vulnerability in the web administration portal, which allows an attacker to execute arbitrary JavaScript via URL. | Medium 6.1 | 21 Feb 2023 |
| CVE-2022-28860 | An authentication downgrade in the server in Citilog 8.0 allows an attacker (in a man in the middle position between the server and its smart camera Axis M1125) to achieve HTTP access to the camera. | Medium 5.9 | 21 Jul 2022 |
| CVE-2022-28861 | The server in Citilog 8.0 allows an attacker (in a man in the middle position between the server and its smart camera Axis M1125) to see FTP credentials in a cleartext HTTP traffic. These can be used for FTP access to the server. | Medium 5.9 | 21 Jul 2022 |
| CVE-2017-20049 | A vulnerability, was found in legacy Axis devices such as P3225 and M3005. This affects an unknown part of the component CGI Script. The manipulation leads to improper privilege management. It is possible to initiate the attack remotely. | Critical 9.8 | 15 Jun 2022 |
| CVE-2022-23410 | AXIS IP Utility before 4.18.0 allows for remote code execution and local privilege escalation by the means of DLL hijacking. IPUtility.exe would attempt to load DLLs from its current working directory which could allow for remote code execution if a compromised DLL would be placed in the same folder. | High 7.8 | 14 Feb 2022 |
| CVE-2021-31988 | A user controlled parameter related to SMTP test functionality is not correctly validated making it possible to add the Carriage Return and Line Feed (CRLF) control characters and include arbitrary SMTP headers in the generated test email. | High 8.8 | 5 Oct 2021 |
Original policy
Copied from bugcrowd.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Description
Axis Communications acknowledges the importance and hard work performed by security researchers. Thank you for working with us to help increase the security in our products and joining into our program! Report Assessment and Bounty Calculations: This program will use the CVSS v3.1 rating system (Common Vulnerability Scoring System). Axis may assess the vulnerability accordingly to its relevance in the context of how Axis recommends deploying its products, software, and services. In any instance where an issue is downgraded or upgraded, a full, detailed explanation will be provided. Axis will validate all submissions against the latest AXIS OS 13 device software available on axis.com . Vulnerabilities that affect only earlier software versions are out of scope and are not eligible for a bounty. P1 = CVSSv3.1 critical (9.0 – 10.0) P2 = CVSSv3.1 high (7.0 – 8.9) P3 = CVSSv3.1 medium (4.0 – 6.9) P4 = CVSSv3.1 low (0.1 – 3.9) Reward payout: Rewards are paid out directly once the submission is accepted as valid submission. Researchers will also receive a one-time-only swag reward in form of a AXIS M1075-L free of charge (MSRP $350) for submissions that result in a CVE-ID. An additional bonus of up to $10.000 may be rewarded for exceptional submissions to Axis discretion. The maximum bonus will always be rewarded in accepted P1/Critical submissions. Bypass reward We welcome submissions that can bypass previously disclosed AXIS OS CVEs. If your submission is deemed valid, you will be eligible for a one-time reward of $500 per CVE. If you share new insights or techniques that increase the impact of the CVE, we'll reassess the vulnerability. In these cases, the payout will match the updated severity level, which could exceed the $500 reward. Disclosure Policy: Axis as authorized Common Vulnerability and Exposures (CVE) Numbering Authority (CNA) discloses all vulnerabilities found in the Bug Bounty Program accordingly as outlined in the Axis Vulnerability Management Policy . Eligibility and Fairness: To maintain the integrity and fairness of our bug bounty program, individuals who are currently employed by Axis or who were previously employed by Axis, are not eligible to receive rewards for vulnerabilities identified through the use of internal knowledge gained during their employment. If you are aware of a vulnerability as a result of current or past employment, we still encourage you to disclose it responsibly. While such reports may not qualify for a monetary reward, they will be reviewed and addressed with the same level of priority as all other submissions. We appreciate your cooperation in helping us ensure a transparent and equitable program for the wider security research community. By participating in this program, you acknowledge and agree that Axis may enforce Bugcrowd’s Standard Disclosure Terms if you breach any provision therein. Axis EULA applies when accessing Axis devices through the Bug Bounty Program .
Targets
In-Scope Products All targets accessible in the Target & Access Information. All Axis-branded products, software and services that are not listed in the In-Scope Products section are automatically out of scope. Out-of-Scope Vulnerabilities It is by design that selected VAPIX (e.g. BasicDeviceInfo.cgi) and ONVIF (e.g. WSDLs) API endpoints provide basic device information such as software version, model number and other information that do not require authentication to access and are available anonymously. Access to the device is granted through the SSH console to allow researchers to test efficiently. Vulnerabilities requiring local system access, including system-level issues such as D-Bus authorization bypasses, are out of scope unless they enable vertical privilege escalations. For example, escalations from VAPIX users to the Linux root user and from regular SSH users to the root user. Vulnerabilities caused by user configurations that could be prevented by following the Axis OS Hardening Guide . User uploaded created content or applications, for instance ACAPs that can be uploaded and run on Axis devices. Social-engineered attacks such as Cross-Site Request Forgery (CSRF) or Cross-Site scripting (XSS) vulnerabilities and/or that trick the user into accessing a malicious website or clicking on a disguised link while accessing the web interface of Axis devices. Vulnerabilities in Axis-branded pre-installed or uploaded applications (ACAPs), for instance AXIS Object Analytics or AXIS Video Motion Detection. Vulnerabilities listed by 3rd party network security scanners such as 3rd party and open-source component vulnerabilities or missing HTTP(S) security headers such as X-Frame-Options. Any DoS type attack such as resource exhaustion of a device through normal API usage with modified parameter inputs, high frequency API calls or using slowloris attacks. Errors in API documentation. GUI flaws/errors that can be corrected through the VAPIX/Onvif API. Attacks that depends on Man-in-the-Middle (MitM) conditions. Functionality restricted by feature flags . The targets in this program contain a custom script that makes sure device passwords are reset in a specific interval to ensure access. This script and it's functionality is out-of-scope for this program.
AXIS OS (in scope)
Target & Access Information: You are testing AXIS OS. AXIS OS is our Linux based operating system for edge devices. It is used in more than 400 products. While Axis does currently not provide direct access to embedded devices running the target (AXIS OS) we accept any findings if within scope. Recommendations and how-to API endpoints for testing are documented here VAPIX library Many parameters are listed also under this API endpoint https://ip-address/axis-cgi/param.cgi?action=list. How to manage these parameters see this section in VAPIX library Browsing the built-in web interface of the device and using the F12-browser console can also be used to lookup API endpoints For privilege escalations, accounts with different privileges (administrator, operator, viewer) can be created using the built-in web interface The administrator, operator or viewer accounts can be used for web-interface (HTTPS) and VAPIX/ONVIF API interfaces access only. Do not change the root password or factory default the device.