Fix Cursor.callproc() didn't escape procedure name. (#1206)
There was a possibility of SQL injection when calling a procedure with a string received from an untrusted source as the procedure name.
NOTICE: This change may cause backward compatibility issues. If you specified a procedure name like "dbname.funcname", the previous version called CALL dbname.funcname, but from this version, it will call CALL `dbname.funcname` so you cannot specify procedure name with database name anymore.
Configuration
📅Schedule: (UTC)
Branch creation
At any time (no schedule defined)
Automerge
At any time (no schedule defined)
🚦Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕Ignore: Close this PR and you won't be reminded about this update again.
If you want to rebase/retry this PR, check this box
This PR contains the following updates:
| Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) |
|---|---|---|---|
| [PyMySQL](https://github.com/PyMySQL/PyMySQL) ([changelog](https://github.com/PyMySQL/PyMySQL/blob/main/CHANGELOG.md)) | `==1.1.2` → `==1.1.3` |  |  |
---
### Release Notes
<details>
<summary>PyMySQL/PyMySQL (PyMySQL)</summary>
### [`v1.1.3`](https://github.com/PyMySQL/PyMySQL/blob/HEAD/CHANGELOG.md#v113)
[Compare Source](https://github.com/PyMySQL/PyMySQL/compare/v1.1.2...v1.1.3)
Release date: 2026-05-01
##### Security
- Fix `Cursor.callproc()` didn't escape procedure name. ([#​1206](https://github.com/PyMySQL/PyMySQL/issues/1206))
There was a possibility of SQL injection when calling a procedure with a string received from an untrusted source as the procedure name.
NOTICE: This change may cause backward compatibility issues. If you specified a procedure name like `"dbname.funcname"`, the previous version called `CALL dbname.funcname`, but from this version, it will call ``CALL `dbname.funcname` `` so you cannot specify procedure name with database name anymore.
</details>
---
### Configuration
📅 **Schedule**: (UTC)
- Branch creation
- At any time (no schedule defined)
- Automerge
- At any time (no schedule defined)
🚦 **Automerge**: Enabled.
♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about this update again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
---
This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xNDAuMCIsInVwZGF0ZWRJblZlciI6IjQzLjE0MC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This PR contains the following updates:
==1.1.2→==1.1.3Release Notes
PyMySQL/PyMySQL (PyMySQL)
v1.1.3Compare Source
Release date: 2026-05-01
Security
Fix
Cursor.callproc()didn't escape procedure name. (#1206)There was a possibility of SQL injection when calling a procedure with a string received from an untrusted source as the procedure name.
NOTICE: This change may cause backward compatibility issues. If you specified a procedure name like
"dbname.funcname", the previous version calledCALL dbname.funcname, but from this version, it will callCALL `dbname.funcname`so you cannot specify procedure name with database name anymore.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.