Keenetic Product Security Advisory

Issuer and the Scope: The issuing entity of this Policy is Keenetic GmbH, Berliner Straße 300b, 63067 Offenbach am Main, Germany. This  Policy is established as the standard governing Policy for all Keenetic entities worldwide.

As a security researcher or vulnerability reporter, your work is vital to strengthening the safety of digital products and infrastructures. We created this Coordinated Vulnerability Disclosure (“CVD”) policy to ensure that your findings are treated with respect, handled responsibly, and acted upon quickly. It sets out how Keenetic (referred to as “Keenetic GmbH”, “we”, “us”) will respond to your reports, the assurances you can expect, and the steps that lead to a successful disclosure process.

Furthermore, we want to make sure your contributions are valued. We encourage you to participate in the Keenetic bug bounty program, that offers financial rewards to express our appreciation and encourage continued collaboration.

By participating in this process, you are not only helping to protect users and organizations but also joining a community where your expertise is recognized and rewarded. Together, we can make Keenetic products safer, build trust, and create a stronger digital ecosystem. 

Ⅰ.    Scope of the CVD policy – What do we consider to be a valid vulnerability

A valid vulnerability, in the context of this policy, is understood as a weakness, flaw, or security issue that directly affects one of the Keenetic’s products or infrastructure that can be exploited. 

To qualify as a valid report, the information disclosed should not already be publicly known, thereby ensuring that the report contributes new and actionable knowledge to the security process.  Furthermore, reports that are solely generated by automated tools or scans without sufficient supporting documentation are not considered adequate, as they lack the necessary evidence to enable meaningful analysis and remediation of a valid vulnerability.  Each report should ideally contain supporting details. This helps us focus on real issues and respond faster. 

Ⅱ.    How to report a vulnerability

When you discover a valid vulnerability, file a report by using the following channels. 

Email: You can email us at security@keenetic.com to ensure proper coordination and tracking.

Web Form: We provide a secure web submission form on our vulnerability disclosure page: https://keenetic.com/security/anonymous-reporting-form. This form supports anonymous reporting. You are not required to provide any personal information to submit a report; however, keep in mind that if you report anonymously we will not be able to ask you follow-up questions, which may limit our ability to investigate the issue. The web form is available in English, and it guides you to include the key details we need.

Security.txt: We maintain a keenetic.com/security.txt on our website which lists our vulnerability disclosure contacts and preferences. Reporters can refer to this file for up-to-date information on how to reach us.

When submitting a report, please include as much technical detail as possible. This helps us triage and fix the issue faster. We suggest providing:

• A description of the vulnerability and its potential impact. What could an attacker achieve? Which confidentiality/integrity/availability aspects are at risk? What could be the affected system in Keenetic’s IT infrastructure (e.g. Keenetic Corporate Systems, Operating System, App, Remote Monitoring and Management, Cloud and Keenetic Account)?

• Specific product names, versions, and configurations affected. (For websites or services, include URLs or IPs; for hardware or software, include model or version numbers.)

• Steps to reproduce the issue – e.g. what commands, inputs, or actions trigger the vulnerability. Screenshots or proof-of-concept (PoC) code are very helpful.

• If known, any suggested remediation or references to fixes (optional but appreciated).

• Your contact information (name or alias, and a secure method to reach you) if you desire a response. You may report anonymously, but then we cannot communicate with you for clarification or to give status updates.

Voluntary Information: The reporter may voluntarily provide contact information for coordination but is not required to submit personally identifiable information. You may use our web site based anonymous reporting form.

Ⅲ.    What we expect from you – Code of Conduct

We only reward reporters and acknowledge their achievements under this CVE policy which adhere to high standards of integrity and responsible behavior when discovering and reporting vulnerabilities. Therefore, we do not tolerate the following behavior:

• Good Faith Testing: Reporters shall only conduct testing that is non-disruptive and necessary to confirm the vulnerability's existence (Proof of Concept). They must not intentionally compromise user data, disrupt services, or damage systems.

• No Exploitation Beyond Testing: Active exploitation of a vulnerability beyond initial proof-of-concept testing is strictly prohibited. In particular, do not abuse the vulnerability to compromise data, alter configurations, pivot to other systems, or persistently access our systems. Triggering the issue to prove its existence is sufficient – do not, for example, download more data than necessary to demonstrate the flaw. If you encounter sensitive information (e.g. personal data of users, proprietary material), cease testing and report it immediately to us, and do not disclose or retain that information. 

• No social engineering or physical attacks: Do not use social engineering techniques (phishing emails, phone pretexting, etc.) against our employees or systems, and do not perform any physical security tests (such as attempting to enter our offices or data centers). This policy is limited to technical vulnerabilities in our products and infrastructure, and excludes social and physical attack vectors. 

• No denial-of-service or “brute force attacks”: Refrain from performing DoS/DDoS attacks or any testing that could degrade our services’ availability for users as well as “brute force” attacks. We want to avoid any disruption to our customers.

• No third-party or public attacks: Do not target vulnerabilities in third-party services or products that we use (instead, please notify those vendors directly). Similarly, do not test systems that are not owned or operated by us. If you inadvertently access data or systems of other parties during your research, notify us and cease further action. Do not compromise or manipulate data of any third party during your research. 

• Confidentiality and use of information: Reporters shall keep vulnerability details confidential and shall not publicly disclose, sell, or otherwise distribute exploit code or technical details that would enable exploitation until Keenetic has provided a public advisory or otherwise authorized disclosure. This does not restrict the reporter from notifying competent authorities, national CSIRT, or law enforcement where required by law or where immediate disclosure is necessary to prevent imminent harm.

• Remediation Period: Keenetic shall be afforded a reasonable, remediation period based on severity to investigate, remediate, and distribute security updates. If Keenetic fails to remediate or provide a credible mitigation within a reasonable period, the reporter may notify a national CSIRT or competent authority.

If a reporter inadvertently violates part of this code of conduct, we commit to still handle any discovered vulnerability in good faith to the best of our ability; however, such a reporter might not receive any rewards.

Ⅳ.    Our commitment to you when a vulnerability is reported

All incoming reports are treated to the best extent possible. Therefore, at least one valid contact option should be provided by you when reporting a vulnerability. Of course, you may report a vulnerability anonymously. 

1.   Response

After you submit a vulnerability report to us, we will let you know we received your report. This will be a personal reply from our security team. If we need clarification or additional information, we’ll ask as soon as possible. Be aware, for anonymous submissions, we obviously cannot respond, but we will proceed to investigate. For the transmission of confidential information, we need you to provide at least your email to be able to use our PGP-encryption key available at https://keenetic.com/security.txt

After further analysis of the report, we provide you with feedback as to whether we confirm or reject the reported vulnerability, meaningful queries to understand the reported vulnerability or an explanation why the investigation of the reported vulnerability is taking longer as expected.

2.   Confidential communication

We ensure to the extent permitted by law that each incoming vulnerability report is treated confidential and your personal data will not be disclosed to third parties without your explicit consent.

Information required for the public disclosure of the validated and verified vulnerability is publicly disclosed to the extent we are obliged by law. 

3.   Anonymous reporting (optional)

You may use our web site based anonymous reporting form.

As we respect your wish to remain anonymous, please be aware that anonymous reports can only be processed to a limited extent or possibly not at all, due to the missing option to request technical or content-related queries, especially in the case of complex issues. 

4.   Respectful and open communication

All communication will remain professional and we will treat you with respect. We expect the same courtesy in return – we have zero tolerance for any discrimination, harassment or disrespect in communications from either side.

Our security team may reach out with questions to better understand the issue or request reproducible technical artifacts and instructions so the vulnerability can be reproduced and fixed. We encourage you to ask for updates at any time; we consider follow-up inquiries welcome and a sign of your interest, not an annoyance. 

Ⅴ.    Coordinating and completing the disclosure

Validated and verified vulnerabilities are publicly disclosed by Keenetic. The public notification includes:

• A description of the vulnerability.

• Information allowing users to identify affected products/versions.

• The impact and severity.

• Clear instructions on how to apply corrective measures or a patch.

The coordinated vulnerability disclosure process is considered to be complete, if the vulnerability has been mitigated or fixed by appropriate measures and has been publicly disclosed indications of the vulnerability report are unfounded and, therefore, the report can only be processed to a limited extend or not at all.

We consider a CVD process completed when one of the following occurs: 

• a fix or mitigation has been deployed and a public advisory released; or 

• the reported issue was determined not to be a vulnerability (false positive or out of scope) and this was communicated to the reporter; or 

• we are unable to reproduce or need more info and the reporter is unresponsive for an extended period (generally 30 days), in which case we close the case pending new information. 

We communicate the end of the CVD process to the reporter, unless the vulnerability was reported anonymously.

Ⅵ.    Rewards

We deeply appreciate the efforts of reporters and others who privately report vulnerabilities to us. As a token of thanks, we operate a Bug Bounty Program. External security researchers who responsibly report vulnerabilities in accordance with this policy may be eligible for a financial reward as a token of appreciation. The amount of any reward is determined individually based on the severity of the reported vulnerability as described in our Bug Bounty Terms & Conditions.

Ⅶ.    Legal Safe Harbor

By adhering to this CVD policy, Keenetic acknowledges that the reporter is acting in "good faith" research, and will not pursue criminal charges against the reporter in relation to the research activities.

Keenetic (“Keenetic”, “we”, “us”) operates a Bug Bounty Program (“Program”). The Program is governed by these Bug Bounty Terms & Conditions and by the Coordinated Vulnerability Disclosure Policy (“CVD‑Policy”). Collectively, these documents constitute the binding legal terms of the Program (the “Terms”).

1.    Program Overview

(1)   The Program’s goal is to improve our products’ security and protect user data by leveraging outside expertise, in line with our Terms. By submitting a vulnerability report or otherwise participating, you agree to the Terms.

(2)   A valid vulnerability, in the context of the Terms, is understood as a weakness, flaw, or security issue that directly affects one of Keenetic's products infrastructure that can be exploited. The amount of any reward is determined individually based on the severity of the reported vulnerability.

(3)   The decisions made by Keenetic regarding Bug Bounties are final and binding. Keenetic may change or cancel this Program at any time, for any reason.

2.    Safe Harbour

(1)   We consider activities conducted in compliance with our Terms to be authorized, this means we will not initiate legal action (civil or criminal) against you for your good-faith efforts under the Program.

(2)   Notably, this assurance applies only if you abide by the Terms of the Program – we cannot immunize you from legal consequences initiated by third parties or authorities for actions beyond our scope. You are expected to always comply with applicable laws and refrain from any actions that go beyond what is permitted here. If in doubt about whether an action is allowed, please stop and ask us first (see contact information under “Procedure for Reporting a Vulnerability and Code of Conduct” of Keenetic Coordinated Vulnerability Disclosure Policy.

3.    Scope of the Program

(1)   The Program covers the following products, services, and websites of our organization (“in-scope systems”):

• Web Applications: e.g., our official website and subdomains, customer portals, and online services.
• Mobile/Desktop Applications: The latest versions of our apps (Android, iOS, Windows) distributed via official app stores.
• API & Infrastructure: Publicly documented APIs and backend services we own.
• Hardware/IoT Devices: Any hardware products with their firmware.

(2)   Only vulnerabilities that directly affect these in-scope systems are eligible for rewards. If in doubt whether a system is in-scope, please inquire before testing. We may update the scope from time to time (e.g., adding new targets or temporarily suspending some systems) – such changes will be noted on our Program webpage.

(3)   For avoidance of doubt, the following systems are out of scope, testing them is not authorized (“out-of-scope systems”):

• Third-Party Services or Infrastructure: Vulnerabilities in third-party platforms we use (cloud providers, SaaS tools, etc.) should be reported to those vendors, not to us. Attacks or scans against our vendors or partners are not allowed.
• Assets Not Owned by Us: Any website, application, or system not expressly listed as in-scope (including domains that don’t belong to our company).
• Denial of Service: Any attacks that disrupt service (DoS/DDoS) or brute-force large numbers of requests or login attempts.
• Social Engineering & Physical Attacks: Manipulating our employees or users (via phishing, vishing, etc.), or attempting to gain physical access to offices, are strictly prohibited. The Program is limited to technical vulnerabilities.
• Privacy Violations: Accessing, copying, or modifying data that is not your own. For example, extracting other users’ personal information or proprietary data is out-of-scope even if a vulnerability makes it theoretically possible. If during testing you encounter someone else’s data, stop immediately and report the issue; do not continue exploring that data.

4.    Program Eligibility

(1)   This Program is intended for external security researchers. To participate and receive any bounty, you must meet all of the following eligibility criteria

       a.   Minimum Age
You must be at least 18 years old. If you are 14 or older but under 18 (or under the age of majority in your country), you must have permission from your parent or legal guardian to participate. In any case, no participants under 14 years of age are allowed.

       b.   Individual or Organization Permission
You can participate in an individual capacity or on behalf of your employer. If you are reporting in the course of your employment or using your employer’s resources, ensure your employer permits participation in bug bounty programs. It is your responsibility to review your employment agreements or policies.

       c.   No Current or Recent Employees/Contractors
Employees of Keenetic or its subsidiaries are not eligible. This includes anyone who has left our employment within the last 6 months, as well as anyone currently working for us as a contractor, consultant, or intern with access to our internal systems. Immediate family members (spouse, parent, child, sibling) of our employees are also not eligible. This ensures fairness and avoids conflicts of interest.

       d.   Public Sector
If you are a public sector employee (e.g., government, law enforcement, military, or education sector), you may only participate in your personal capacity and not as part of your official duties. It is your responsibility to ensure that accepting a bounty from us does not violate any laws or ethics rules that apply to you.

       e.   Multiple Reports & Duplicates
If the same vulnerability is reported by multiple researchers, only the first report we receive will be eligible for a Bug Bounty, provided our Terms are met. If a later report contains new information that we were not aware of, we may, at our discretion, award a partial bounty to the later reporter. Please note we might already be in the process of fixing an issue when you report it; if so, we will inform you, and such a case may not qualify for a reward, if we deem it a known issue.

(2)   We reserve the right to disqualify any Participant who does not meet these criteria or who is found to violate the intent of these rules. Bug Bounties will not be paid to anyone who is on a sanctions list or whom it would be legally impermissible for us to compensate. If you have questions about eligibility or need clarification, please contact us.

5.    Procedure for Reporting a Vulnerability and Code of Conduct 

(1)   As laid down comprehensively in the CVD-Policy, Keenetic provides multiple secure channels for reporting valid vulnerabilities, including 

• email - security@keenetic.com, 
• a web submission form at https://keenetic.com/security/anonymous-reporting-form, and 
• a security.txt file hosted on our website.

(2)   Reports should contain comprehensive technical details such as a description of the vulnerability, its potential impact, affected systems, product versions, and steps to reproduce, supplemented by proof-of-concept material where possible.

(3)   Anonymous reporting is permitted; however, it may limit follow-up communication. All reporters are expected to adhere to our Code of Conduct stated in the CVD-Policy, which prohibits e.g., disruptive testing, exploitation beyond proof-of-concept, social engineering, physical attacks, denial-of-service, brute force attempts, and targeting third-party systems.

6.    Rewards

(1)   The Program offers Bug Bounties for eligible, validated vulnerability reports. Our goal is to acknowledge and reward security researchers fairly based on the severity and impact of their findings, while being transparent about how rewards are determined.

(2)   We classify reported vulnerabilities based on their impact and exploitability into the following categories: low, medium, high, and critical. For each category, we have typical reward ranges (in US-Dollar). A typical reward structure may include:

(3)   The actual reward amount for any individual case is determined at the sole discretion of Keenetic after our security team has validated the reported vulnerability and assessed its severity. We consider factors such as the classification and sensitivity as well as amount of affected systems/data, ease of exploitation, and overall risk to our users and organization. 

(4)   No reward will be paid in the following cases:
a.   Lack of Secure/HTTPOnly flags on non-sensitive Cookies;
b.   Duplicate reports of security issues, including security issues that have already been identified internally;
c.   Automated scanning attacks;
d.   Distributed Denial of Service attacks and Denial of Service attacks;
e.   UI, UX bugs, and spelling mistakes, Usability issues;
f.   Violations of licenses or other restrictions applicable to any vendor's product;
g.  Vulnerabilities that are a result of malware;
h.   Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end-user interactions to be exploited;
i.   Vulnerabilities considered to be below a P1 impact;
j.   Discovery of any in-use service whose version contains known vulnerabilities (such as a specific version of Linux Kernel, or OpenSSL) without a demonstration of intrusion, information retrieval, or service disruption using that vulnerability;
k.   Leveraging the findings of one vulnerability to create further exploits to then test normally inaccessible functionality, e.g. using leaked personal data, if there is no evidence that a vulnerability can be leveraged to a greater degree;
l.   Vulnerabilities in third-party software and services.

(4)   If a Participant violates any provision of the Terms, Keenetic may reduce, withhold, or require the return of all or part of any reward paid or payable in respect of the relevant vulnerability. The amount of any reduction shall be proportionate to the severity of the violation and may take into account factors including the nature of the violation, the degree of culpability and any actual or potential harm caused.

7.    Payments

(1)   To receive payment, you will need to provide us with necessary details (such as payment method, tax information if required). Bounties will typically be paid in US-Dollar ($) or, if we specify, in another currency like EUR – we will clarify this during the award process. We can often accommodate a preferred payment currency at the exchange rate at time of payment.

(2)   Please note that Bug Bounties are generally considered taxable income. You are solely responsible for paying any taxes due in your jurisdiction for the reward. We may ask you to fill out certain tax forms (especially if you are in a different country) before payment. If you are unable or unwilling to complete required paperwork, it could delay or forfeit the payment.

8.    Copyright

(1)   You retain any intellectual property rights in respect of your submission. However, by submitting a vulnerability report to us, you grant us a non-exclusive, perpetual, irrevocable, worldwide, royalty-free license to use, modify, test, create derivative works from, share, and publish the information in your report for the purpose of addressing the vulnerability and improving security. 

(2)   For example, we can use the submitted proof-of-concept code to reproduce the issue, we can disclose details to a third-party vendor if needed (to coordinate a fix in a component), and we can include relevant details in our public advisories. You also agree that any materials you submit are either your original work or you have the legal right to provide them.

9.    Restrictions on Disclosure

(1)   We will investigate the vulnerability that you have reported and will aim to resolve it as quickly as possible. If you wish to publish details of your findings, please contact us first for approval. For 30 days after the vulnerability is fixed, we require that you withhold detailed proof-of-concept exploit code and any other information that could facilitate attacks on our digital products. Keenetic will notify you when the vulnerability in your submission has been fixed.

(2)   Any breach of this section may obligate you to repay bounties awarded for the vulnerability and may result in your exclusion from future participation in the program.

10.   Liability

(1)   Our liability for breaches of the Terms and for tort shall be limited to intent and gross negligence.

(2)   The limitation of liability referred to in paragraph 1 shall not apply to

       a.   injury to life, body and health of the Participant or

       b.   claims of the Participant for breach of cardinal obligations, i.e. obligations arising from the nature of the Terms and the breach of which endangers the achievement of the purpose of the Program. In this case, however, our liability shall be limited to compensation for the foreseeable, typically occurring damage.

In these cases, we shall be liable for any degree of fault.

(3)   Furthermore, the limitation of liability from paragraph 1 shall not apply if a defect was fraudulently concealed.

(4)   Insofar as liability for damages against us is excluded, this shall also apply with regard to the personal liability for damages of our employees, representatives and vicarious agents.

11.   Miscellaneous

(1)   Should any provision of the Terms be or become invalid, the validity of the remaining provisions shall remain unaffected. In place of the invalid provision, a provision shall be deemed to have been agreed which comes closest to the economic purpose of the invalid provision.

(2)   The Terms shall be governed by and construed in accordance with the laws of the Federal Republic of Germany. The statutory provisions restricting the choice of law and the applicability of mandatory provisions, in particular those of the country in which the Participant as a consumer has the habitual residence, remain unaffected.

(3)   If the Participant is a merchant, a legal entity under public law, or a special fund under public law, the place of jurisdiction for all disputes arising from the Terms is Frankfurt am Main, Germany.

Advisory ID: KEN-PSA-2025-WP01
Severity: High
CWE: CWE-521 (Weak Password Requirements)
Status: Resolved in KeeneticOS 4.3 and later

Summary

Before KeeneticOS 4.3, users could set weak admin passwords and still open the router’s web interface to the Internet, which posed a high risk of compromise. Recent internal investigations have revealed that this vulnerability is being exploited by automated password scanners on devices with the most common weak passwords. The latest KeeneticOS 4.3 enforces stronger passwords and blocks public web access if a known compromised password is set.

We have identified that a significant number of users continue to rely on weak or easily guessable passwords. This creates substantial security risks, including unauthorized access, data breaches, and potential service disruptions. Protecting user’s data is our highest priority, and addressing these vulnerabilities is essential.

To strengthen overall security and ensure continued protection of user data, a mandatory software update will be deployed for devices running KeeneticOS earlier than 4.3 in accordance with article 6 of the End User Licence Agreement and in alignment with the EU Cyber Resilience Act (CRA). This update includes enhanced security measures, tools to support stronger password creation, and critical bug fixes that improve system stability and safeguard user accounts.

We sincerely apologize for any inconvenience caused by this update. To minimize disruption, we are trying to implement it outside of standard business hours. If you have any questions or need help, please contact our support team.

Affected Products / Configurations

Products: Keenetic routers running versions of KeeneticOS earlier than 4.3.

Configuration prerequisite: The router's web interface must be exposed to the Internet and remote web access must be enabled.

Vulnerability Details

Issue: Weak administrative passwords are accepted while the web UI can be accessed from the Internet.

Impact: Full administrative takeover of the device, enabling configuration changes, traffic interception/redirection, enabling additional services, and possible further penetration into the internal network.

Vector: Remote (Internet); no prior authentication or user interaction required.

Contributing factors: Exposure of the admin interface to the Internet and weak, easily guessable credentials.

Severity (CVSS v3.1 — analyst estimate)

8.8 (High) — AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
Rationale: Remote, unauthenticated path to admin control when weak passwords are permitted; availability impact is secondary to confidentiality/integrity.

Remediation & Hardening

Platform controls: The device automatically checks whether the administrative password is on the list of the most commonly used weak passwords. In this case, it blocks remote access to the web interface and execution of custom software, and the password can only be changed from the local area network. When entering a new password, the device enforces password strength according to NIST SP 800-63B recommendations.

Upgrade: Transfer all devices running versions earlier than 4.3 to KeeneticOS 4.3 or later. Use the latest OS available for your model.

Admin credentials: Use long, unique passwords. We recommend at least 15 characters or a generated passphrase.

Limit exposure: If remote web access isn’t strictly necessary, disable it. Use firewall rules to allow access to the device's web interface only from specific IP addresses.

Monitor for attacks: Watch out for repeated failed logins or lockouts, as these could be an indication of a brute-force attack.

Advisory ID: KEN-PSA-2025-WA01
Severity: Medium
CVE: CVE-2025-56007, CVE-2025-56008, CVE-2025-56009
Status: Resolved in KeeneticOS 4.3 and later

Keenetic has received and verified reports of three severe security vulnerabilities affecting all versions of KeeneticOS before 4.3. An independent security researcher responsibly disclosed these vulnerabilities, which have since been addressed in the latest stable release.

The vulnerabilities are identified as CVE-2025-56007, CVE-2025-56008, CVE-2025-56009.

CVE-2025-56007 — CRLF Injection at /auth API Endpoint:
A CRLF injection vulnerability in the /auth API endpoint could allow remote attackers to manipulate HTTP headers and inject unauthorized commands. Attackers could add new administrative users and gain control of the device by tricking a victim into opening a specially crafted page.

CVE-2025-56008 — Cross-Site Scripting (XSS) on “Wireless ISP” Page:
Attackers could exploit an XSS vulnerability on the “Wireless ISP” configuration page by broadcasting a specially crafted SSID containing malicious script. When the user scans for available networks using the Web interface, the script is executed in the context of the administrator’s session, enabling the attacker to gain control of the device.

CVE-2025-56009 — Cross-Site Request Forgery (CSRF) at /rci API Endpoint:
A CSRF vulnerability in the /rci API endpoint could allow attackers to perform unauthorized actions on behalf of an authenticated user. By luring the victim to visit a malicious page, attackers could silently add users with full permissions and compromise the device.

Potentially affected devices:
All Keenetic models with the “KN” index, released from 2017 onwards.

Severity:
The severity is considered medium, as the user must be logged into the router's web interface during the attack. An attack on the “Wireless ISP” page also requires the attacker to be close to the device.

Affected firmware versions:
All KeeneticOS versions up to 4.2.

Solution:
All users are strongly advised to upgrade their Keenetic devices to the latest stable firmware version, KeeneticOS 4.3, which includes patches for these vulnerabilities. Firmware updates can be performed via the device’s web interface or Keenetic mobile app.

Acknowledgments:
We thank the independent researcher for their responsible disclosure and contribution to improving the security of Keenetic products.

Advisory ID: KEN-PSA-2025-WD01
Severity: Medium
CVE: CVE-2025-20674, CVE-2025-20685, CVE-2025-20686
Status: Resolved in KeeneticOS 4.3.2 and later

Keenetic is aware of an “Arbitrary Packet Injection” vulnerability in the Wi-Fi AP driver, reported by the chipset maker, Mediatek, Inc. There is a possible way to inject an arbitrary packet due to a missing permission check. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

The chipset manufacturer also reported additional vulnerabilities, such as a possible out-of-bounds write due to an incorrect bounds check. This could lead to remote code execution with no additional execution privileges needed.

The vulnerabilities are identified as CVE-2025-20674, CVE-2025-20685, CVE-2025-20686.

Potentially affected devices:
All Keenetic models with the “KN” index, released 2017 onwards, are based on Wi-Fi chipsets produced by Mediatek: MT7628, MT7603, MT7612, MT7613, MT7915, MT7916.

Affected firmware versions:
All KeeneticOS versions up to and including 4.3.1

Severity:
The severity is considered medium, as the attacker has to be in close physical proximity to the target device.

Solution:
KeeneticOS 4.3.2 includes necessary fixes addressing these vulnerabilities. This update applies to all affected Keenetic models. We strongly recommend users upgrade their devices to the latest KeeneticOS version available online. Keenetic has already begun rolling out automatic updates to devices that have the auto-update option enabled.

Advisory ID: KEN-PSA-2025-CS01
Severity: Medium
Status: Resolved

In light of newly discovered information, Keenetic Limited informs Keenetic Mobile App users who registered before March 16th, 2023, that part of their mobile app data may have been compromised due to unauthorized database access.

On the morning of March 15th 2023, we were informed by an independent IT security researcher about the possibility of unauthorized access to the Keenetic Mobile App database. After verifying the nature and credibility of the risk, we immediately resolved the issue on the afternoon of March 15th 2023. The IT security researcher assured us that he hadn't shared any data with anybody and destroyed it. Since then, we had no indication that the database was compromised or any user was affected until the end of February 2025.

On February 28, 2025, we learned that some database information had been disclosed to an independent media outlet. Therefore, we have determined that we can no longer guarantee the data was properly destroyed, and some information may now be beyond our control.

However, due to the nature of the data that could be potentially exposed, we estimate the risk of fraudulent activity to be low.

A limited number of database fields were accessible: Keycloak IDs, emails (logins) and names of Keenetic accounts, locales; device user account configurations, including MD5 and NT password hashes; custom KeenDNS names; network interface configurations, including Wi-Fi SSIDs and preshared keys; Wi-Fi channel settings, roaming IDs and keys; IP policy and traffic shaping settings; remote peer addresses, logins and passwords of VPN clients, assigned IP addresses; names and MAC addresses of registered hosts; IPsec site-to-site configurations; IPsec Virtual-IP server configurations; DHCP pool settings; NTP settings; IP and MAC access lists.

To our best knowledge, no other data has been accessible. In particular, RMM data, Keenetic account data, private keys and configurations of Wireguard VPN tunnels, and OpenVPN data were inaccessible.

Keenetic doesn't collect, store, or analyse data on payment card details or related credentials, transactional data, banking details, or banking passwords. Thus, such data is not affected.

We recommend to these Keenetic mobile app users to change following passwords and pre-shared keys:

- Keenetic device user account passwords (link to the instruction);

- Wi-Fi passwords (link to the instruction);

- VPN-client passwords/pre-shared keys for: PPTP/L2TP (link to the instruction), L2TP/IPSec (link to the instruction), IPSec Site-to-Site (link to the instruction), SSTP (link to the instruction).

We strongly believe that unauthorized access happened without any fraudulent or malicious intent, and database information is not available to the public, nevertheless, appropriate notification was sent to the relevant data protection authority.

We apologize for any inconvenience and confirm that all the necessary actions have been taken to prevent a similar situation in the future.

We set security as our highest priority to deliver a protected and controllable environment to safeguard our users’ networks and data. We constantly work on improving our operating system, applications and cloud infrastructure. With regular updates, we continually enhance performance and security to ensure that our software stays up-to-date.

If you have any questions, please do not hesitate to contact the relevant technical support team.

Advisory ID: KEN-PSA-2024-ED01
CVE: CVE-2024-4021, CVE-2024-4022
Severity: Low
Status: Resolved in KeeneticOS 4.3 and later

Keenetic was notified early and is fully aware of vulnerabilities CVE-2024-4021 and CVE-2024-4022.

Potentially affected devices:
- KN-1010
- KN-1410
- KN-1711
- KN-1810
- KN-1910

Affected firmware versions:
All KeeneticOS versions up to and including 4.1.2.15.

Clarification of the reported vulnerabilities:
1. CVE-2024-4022 refers to a reported disclosure of information intended to be publicly available. Displaying the model name and firmware version in the web interface is done by design and is not considered a vulnerability. The model name is explicitly shown on the user interface, and the firmware version can easily be approximated due to frequent updates, which visibly change the interface.
2. CVE-2024-4021 does not enable remote access, control, or leakage of private user information. Instead, it allows an attacker to identify which software components (e.g., WPA3-E, WireGuard, OpenVPN) are installed on the router. Importantly, this vulnerability does not indicate whether these components are active or enabled. It also does not disclose if a specific service is being provided externally (for example, WireGuard could be available through port forwarding rather than installed on the router itself). After consulting an independent third-party security researcher, Keenetic classified this vulnerability as low-risk information disclosure. This means it does not directly compromise the device or user information.

Severity:
The severity of disclosure of excessive information about the device and operating system is considered low.

Solution:
Due to the low-risk nature of these vulnerabilities, Keenetic will address these issues in the next KeeneticOS update. A fix will be included in KeeneticOS version 4.3, scheduled for release by mid-2025. An urgent update is not required.

Advisory ID: KEN-PSA-2021-WD01
Severity: Medium
CVE: CVE-2020-24586, CVE-2020-24587, CVE-2020-24588, CVE-2020-26139, CVE-2020-26140, CVE-2020-26146, CVE-2020-26147
Status: Resolved in KeeneticOS 3.6.6 and later

Keenetic is aware of the Wi-Fi security vulnerabilities known as FragAttacks (Fragmentation and Aggregation Attacks). Detailed information can be found at https://www.fragattacks.com.

The following vulnerabilities have been identified:
- CVE-2020-24586
- CVE-2020-24587
- CVE-2020-24588
- CVE-2020-26139
- CVE-2020-26140
- CVE-2020-26146
- CVE-2020-26147

Potentially affected devices:
All Keenetic models with the “KN” index, released from 2017 onwards.

Affected firmware versions:
All KeeneticOS versions up to and including 3.6.5.

Severity:
The severity of FragAttacks is considered medium, with a wide-ranging impact on nearly all Wi-Fi devices since 1997. The vulnerabilities can potentially lead to information disclosure and privilege escalation. However, exploiting them is not straightforward and requires the attacker to be in close physical proximity to the target device.

Solution:
KeeneticOS version 3.6.6 includes necessary fixes addressing these Wi-Fi vulnerabilities. This update applies to all affected Keenetic models. We strongly recommend users upgrade their devices to the latest KeeneticOS version available online. Keenetic has already begun rolling out automatic updates to devices that have the auto-update option enabled.