E-Business Suite alone gets 194 patches, 31 of them exploitable without a login, led by an Application Object Library flaw rated 9.8. Fusion Middleware gets 206, MySQL 98 and Java SE 55.
Google Data Studio will stop connecting to MySQL 5.6 and 5.7 after 26 February 2027
EditorialBy TrustList Editorial
After 26 February 2027, Data Studio (formerly Looker Studio) will not create new MySQL 5.6 or 5.7 data sources, and existing reports on them "might not properly load data". Upgrade to MySQL 8.0 or later.
About Google Data Studio will stop connecting to MySQL 5.6 and 5.7 after 26 February 2027
Google Data Studio will stop connecting to MySQL 5.6 and 5.7 after 26 February 2027
24 September 2026: Google has announced the end of support for MySQL 5.6 and 5.7 in the MySQL connector of Data Studio, the free reporting tool formerly called Looker Studio. The release note is dated 24 September 2026, and the connector's documentation, updated the same day, now marks both versions as "sunsetting".
What changes
After 26 February 2027:
- users can no longer create new Data Studio data sources that connect to MySQL 5.6 or 5.7;
- existing data sources and reports on those versions "might not properly load data", in Google's words.
Google points users to MySQL 8.0 or 9.0. Both older versions are already past the end of Oracle's own support for MySQL, so the databases concerned are often ones that nobody has upgraded for years.
Who is affected
Any team whose Data Studio dashboards read directly from an older MySQL server. That commonly includes sales and marketing dashboards built on a website or e-commerce database, reports built by an agency, and reporting from older managed database instances in the cloud. The risk is quiet failure: a dashboard that stops loading, or loads incomplete figures, in a board meeting in March.
What to do
- List the Data Studio data sources that use the MySQL connector, and check the server version behind each one.
- For each on 5.6 or 5.7, either upgrade the database or point the report at a replica running 8.0 or later before 26 February 2027.
- If an agency built your reporting, ask it to do the same check across the reports it maintains for you.
- Treat an old MySQL version found this way as a security question too, not only a reporting one.
Not yet independently verified. This rests on Google’s own release note and connector documentation. No independent report of it was found, so every date here comes from the vendor's own page and is only as reliable as that page. We will update this when it can be confirmed, and remove this note.
Related on TrustList:
Sources
- Google Cloud release notes, entry dated 24 September 2026 (read 25 September 2026) - 24 September 2026
- Google Cloud: Connect to MySQL, Data Studio (last updated 24 September 2026) - 24 September 2026
Categories & features
TrustList Weekly
The week in software and IT, in one email
The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.
You may be interested in
An attacker used a compromised GitHub account and leaked credentials for four weeks, copying customer contacts, contract terms, SQL editor text and encrypted API keys. PingCAP says the databases themselves were not reached.
The flaws range from NoSQL injection to silent loss of client-side encryption and shared connections across client certificates. Several fixes change driver behaviour, so test before upgrading.
DuckDB 2.0 is supported until at least October 2027 and 1.5 has been extended to March 2027. Files written by 2.0 cannot be read by any older version, so upgrade order matters.
Packages for those minor releases, including PostgreSQL 18, move to the YUM archive and get no further updates; servers on RHEL, Rocky Linux or AlmaLinux 10.0 or 9.6 should move to a newer minor release.
Every release from 08.01.0102 to 18.00.0004 is affected. An application that builds IN lists from user input can be crashed, or left running on a corrupted heap.
A user who knows one SCRAM password can log in as any other SCRAM user, superusers included, on PgBouncer 1.17.0 to 1.26.0. Two further flaws let unauthenticated clients hang the pooler under specific settings.
The project had planned an October release. Between eight and ten features, including SQL/PGQ graph queries, were pulled from the branch during beta and move to PostgreSQL 20.
More on TrustList
Everything here links back to the same verified catalogue. Pick your next stop.
- More MySQLThe ranking for this subject
- CompaniesAgencies, consultancies and IT service providers, ranked by verified reviews.
- ProductsSoftware and SaaS with pricing, features, integrations and alternatives.
- AwardsAnnual recognition decided by verified reviews and an independent jury.
- LaunchesNew products and releases, voted up by the community every day.
- AI ModelsBenchmark scores and community ratings for every major model.
- RequestsBuyers describe what they need; vendors respond directly.
- PeopleReviewers, authors and makers with public profiles.
- ComparePut up to four listings side by side before you shortlist.