The MySQL security vulnerability published on November 17, 2026 affects Oracle’s MySQL Server and MySQL Cluster, with a severity score of 9.1 out of 10 assigned by the reporting organization (CNA) per the NVD entry. If your website, management software, or accounting system runs on MySQL, check which version is installed.
What is it?
CVE-2026-114952 allows, in certain versions, data in a MySQL database to be read or altered remotely, without supplying a password.
MySQL is database software, the digital filing cabinet where a business stores customer records, invoices, or appointments. It’s a bit like closing the cottage for winter: you lock the door and leave with peace of mind, but one window latch never quite caught. Per the NVD entry, the flaw sits on the client side, meaning the tools that connect to the database to read or write data. It can be exploited easily by someone who is not authenticated and has no account on your system.
Why is it serious?
Because the attack requires neither a password nor any action from your employees, and data can be read as well as altered.
The 9.1-out-of-10 score comes from the reporting organization (CNA) per the NVD entry. The breakdown of that score describes impacts on data confidentiality and integrity, with no impact noted on availability. That does not mean your software is guaranteed to keep running normally. In business terms, this means quiet risks: a leak of information about your customers or employees, and tampered data, such as altered invoice amounts, which opens the door to fraud. No exploitation is reported in the records reviewed as of the review date.
Who is affected?
MySQL Server versions 8.4.0 through 8.4.13, 9.7.0 through 9.7.4, and 26.10, as well as MySQL Cluster 8.0.0 through 8.0.50, 8.4.0 through 8.4.13, 9.7.0 through 9.7.4, and 26.10.
MySQL can be present in your business without your knowledge, because it’s embedded in a transactional website, an appointment-booking tool, an invoicing system, or an inventory management application. Auto shops, clinics, carriers, accounting firms, and retailers can all be affected the same way.
How do I check my business?
A few simple questions, asked to the right people, are enough to know whether you’re exposed.
- Take inventory of the software that relies on a MySQL database, including your website and accounting system (IT provider).
- Identify the exact installed version and compare it against the ranges published by the NVD (IT provider).
- Ask whether the database server is reachable from the internet, and have that access closed if it isn’t needed (IT provider or hosting provider).
- Ask each software vendor in writing which version of MySQL they use and when they will deliver a fix (management).
Scenario
Fictional example: a dental clinic whose appointment-booking software runs on an affected version of MySQL.
The server had been made accessible from outside so the office manager could check the schedule remotely. Nothing had been verified: no one knew MySQL was running underneath the software. Patient records are accessed, and a few suppliers’ banking details are altered. The clinic closes for a day to verify the integrity of its records, has to notify the people affected, log the incident, and recover payments sent to the wrong account details.
What to do now
- Confirm with your provider that you have a recent, already-tested backup of the MySQL data.
- Review Oracle’s security advisory with your provider to find out which versions are fixed and which patches are available, then plan next steps.
- Restrict network access to the database for as long as the issue isn’t resolved.
- Log the steps taken, with dates and versions, in your internal record.
What this MySQL security vulnerability means for a Quebec organization
A MySQL database often contains personal information. In Quebec, the Act respecting the protection of personal information in the private sector requires organizations to maintain a register of confidentiality incidents. When there is a risk of serious harm, it also requires notifying the people affected and the Commission d’accès à l’information (Quebec’s privacy regulator). These obligations apply to incidents. Taking inventory of your databases is not itself a legal requirement, but it’s the practical step that lets you meet those obligations. We’ll say it again: no protection is absolute, and no provider can guarantee zero risk.
FAQ
Our software is hosted with a provider. Are we affected?
Possibly, yes. External hosting shifts the technical work, not your responsibility to your customers. Ask the provider in writing whether MySQL Server or MySQL Cluster is in use, which version, and where they stand on addressing the issue. Keep their reply on file: it documents your due diligence.
No exploitation has been reported. Can we wait for the next maintenance visit?
We don’t recommend it. The absence of reports in the records reviewed, as of the review date, means none has been reported there, not that none will occur. Patching a database outside business hours is simpler than checking the integrity of customer records after the fact.
Which version should we install?
The fixed version isn’t specified in the NVD entry or in the facts we verified. Oracle’s security advisory is what you should review with your provider, without assuming its contents in advance. The affected ranges span several version families, so the answer depends on which one you’re running.
Sources
- CVE-2026-114952 entry, National Vulnerability Database · NIST, November 17, 2026
- Security advisory (oracle.com) · oracle.com
- Canadian Centre for Cyber Security: baseline cyber security controls for small and medium organizations · baseline control checklist
- Commission d’accès à l’information du Québec · obligations, incident register, and notification
Source: NVD (NIST) · https://nvd.nist.gov/vuln/detail/CVE-2026-114952
This article was prepared by RISS Canada’s threat monitoring team from the public sources cited above, with the assistance of artificial intelligence tools, then reviewed under our editorial standards.



