prepare version info for PMM 3.3.1 (#421)

Author: idoqo

sources/metadata/pmm-server/3.3.1.yaml

@@ -0,0 +1,6 @@
+version: 3.3.1
+imageInfo:
+  image_path: "perconalab/pmm-server:3.3.1"
+  image_hash: "sha256:sha256:e6e8dcd204ca3856bfb1bed68c6e36a57079267340ae1b204ee7bf16679c0e94"
+  image_release_timestamp: "2025-07-30T12:45:00.000000Z"
+  status: "available"

sources/metadata/pmm-server/3.4.0.yaml

@@ -1,6 +1,6 @@
 version: 3.4.0
 imageInfo:
   image_path: "perconalab/pmm-server:3-dev-latest"
-  image_hash: "sha256:1e557afe86ea086647738e0610dfb460017d07ac94c5a9c3a0a186511f5e112d"
-  image_release_timestamp: "2025-07-19T11:00:00.000000Z"
+  image_hash: "sha256:sha256:c6610c784321239cceee623b57378d011248886092fce050a1867d65f8747f22"
+  image_release_timestamp: "2025-07-30T13:50:00.000000Z"
   status: "available"

sources/release-notes/pmm/3.3.1.md

@@ -0,0 +1,73 @@
+# Percona Monitoring and Management 3.3.1
+
+| **Release date** | July 30th, 2025                                                                                                                         |
+|------------------|:----------------------------------------------------------------------------------------------------------------------------------------|
+| **Installation** | [Installing Percona Monitoring and Management](https://docs.percona.com/percona-monitoring-and-management/3/quickstart/quickstart.html) |
+| **Upgrade**      | [Migrate PMM 2 to PMM 3](https://docs.percona.com/percona-monitoring-and-management/3/pmm-upgrade/migrating_from_pmm_2.html)            |
+
+Percona Monitoring and Management (PMM) is an open source database monitoring, management, and observability solution for MySQL, PostgreSQL, and MongoDB. PMM empowers you to:
+
+- monitor the health and performance of your database systems
+- identify patterns and trends in database behavior
+- diagnose and resolve issues faster with actionable insights
+- manage databases across on-premises, cloud, and hybrid environments
+
+## RCE vulnerability in PMM - Immediate action required
+
+We have identified a critical Remote Command Execution (RCE) vulnerability affecting all PMM 2.x and PMM 3.x installations. This vulnerability allows users with CLI access to PMM Client nodes or those with admin-level privileges to exploit the API and execute unauthorized commands on registered nodes.
+
+### Affected installations
+
+This vulnerability affects all PMM 2.x and 3.x deployments where PMM Client nodes are connected to the PMM Server. The security flaw originates from the `pt-mysql-summary` tool, a component of the Percona Toolkit that automatically collects MySQL system information and diagnostics from PMM Client installations.
+
+| **Affected deployments**                              | **Version**         | **Notes**                                                                                                   |
+|-------------------------------------------------------|---------------------|-------------------------------------------------------------------------------------------------------------|
+| All PMM installations with connected PMM Client nodes | PMM 2.x and PMM 3.x | Remote Command Execution vulnerability through `pt-mysql-summary` tool deployed when setting up PMM Clients |
+
+### Remediation options
+
+=== "RECOMMENDED: Upgrade to PMM 3.3.1" This release directly fixes the vulnerability and enhances overall security in all PMM deployments. To upgrade: {.power-number}
+
+```
+1. Schedule a maintenance window to minimize disruption.
+2. [Download the latest PMM release](https://www.percona.com/downloads).
+3. [Upgrade PMM Server](https://docs.percona.com/percona-monitoring-and-management/3/pmm-upgrade/index.html), then [upgrade PMM Client](https://docs.percona.com/percona-monitoring-and-management/3/pmm-upgrade/upgrade_client.html).
+4. Change all credentials for the services that PMM monitors, including database user accounts and any other credentials (e.g., API keys, SSH keys) PMM uses to connect to your infrastructure.
+5. Thoroughly check access logs for any potential unauthorized access attempts or suspicious activity.
+```
+
+=== "TEMPORARY: If you cannot upgrade immediately" If you are unable to upgrade to PMM 3.3.1 immediately, implement one of the following temporary measures to reduce risk. These options do not eliminate the vulnerability entirely. **Prioritize upgrading to PMM 3.3.1 as soon as possible**. {.power-number}
+
+```
+1. Choose one of the following temporary mitigation options:
+
+    - Make `pt-mysql-summary` script non-executable to keep the system information tool on disk but prevent it from being executed via the vulnerable path:
+
+    ```sh
+    sudo chmod -x /usr/local/percona/pmm/tools/pt-mysql-summary
+    ```
+
+    - Delete `pt-mysql-summary` to permanently remove the vulnerable tool from your system:
+
+    ```sh
+    sudo rm -f /usr/local/percona/pmm/tools/pt-mysql-summary
+    ```
+```
+
+### Dashboard impact
+
+```
+        Both options impact the **MySQL Instance Summary** dashboard. Since `pt-mysql-summary` collects system information, disabling or removing this tool will remove CPU, memory, disk, and OS version information from the dashboard. Other performance metrics continue to be collected normally.
+
+2. Change all credentials for the services that PMM monitors, including database user accounts and any other credentials (e.g., API keys, SSH keys) PMM uses to connect to your infrastructure.
+3. Thoroughly check access logs for any potential unauthorized access attempts or suspicious activity.
+```
+
+### Support & additional resources
+
+We are available to assist you 24/7 if you need further clarification or assistance:
+
+- [Technical support portal for customers](https://percona.service-now.com/percona?id=percona_login)
+- [Technical support for community](https://forums.percona.com/c/percona-monitoring-and-management-pmm)
+
+We will continue to provide updates as new information becomes available.