๐ RPA Framework 33.0.1
Breaking changes
RPA.Desktop.Windowshas been removed (#1343). The pywinauto-based library has emitted a deprecation warning pointing at RPA.Windows for a long time and is no longer maintained. Use RPA.Windows for all Windows UI automation going forward.
This is not a drop-in rename. RPA.Windows is built on UIAutomation rather than pywinauto, so keyword names, arguments and locator syntax differ โ expect to rewrite the affected steps rather than just change the import:
The two examples/windows-* scripts that depended exclusively on the removed pywinauto API were removed along with the library.
Security fixes
-
RPA.Archive: Fixed a Zip Slip path traversal vulnerability (CWE-22) inExtract Archive(#1341, fixes #1339, #1340). Archive members containing path traversal sequences such as../../evil.pycould previously be written outside the requested destination directory. Extraction now validates that every member resolves inside the destination first and raisesValueErrorotherwise. Both the ZIP and TAR code paths are covered, for whole-archive and selected-membersextraction alike. -
Dependency bumps across the affected packages:
soupsieveโฅ2.8.4 โ HIGH, memory exhaustion via large comma-separated selector lists (CVE-2026-49476) (#1342)pillowโฅ12.3.0 โ HIGH, heap out-of-bounds write inImageCmsTransform.apply()(CVE-2026-59205) and a decompression-bomb DoS inPdfParser.PdfStream.decode()(CVE-2026-59200)cryptographyโฅ50.0.0 โ HIGH, Bleichenbacher oracle in PKCS#7EnvelopedDatadecryption (CVE-2026-69247)pypdfโฅ6.15.0 โ MEDIUM, excessive memory use for large/ToUnicodestreams (CVE-2026-71870), in rpaframework-pdfpyasn1โฅ0.6.4 โ HIGH, BER/CER/DER decoder DoS via unbounded long-form tag IDs (CVE-2026-59884), andhttplib2โฅ0.32.0 โ HIGH, decompression-bomb DoS via unbounded gzip/deflate handling (CVE-2026-59939), both in rpaframework-googlesetuptoolsโฅ83.0.0 โ MEDIUM,MANIFEST.inexclusion bypass via Unicode normalization collision (CVE-2026-59890), in rpaframework-sema4ai
The
pillowandcryptographyfloors were raised across all packages (#1350, #1338).
Fixes and improvements
-
rpaframework-core: Fixed the Windows locator parser silently mis-tokenizing a strategy when the locator value carried a stray
locator=prefix or an unmatched quote character โ for example producing a boguslocator='executablestrategy instead of recognizingexecutable:. A clearer warning is now surfaced when this happens (#1343, fixes #1323). -
rpaframework-core:
executable:locators are now matched case-insensitively. Windows file names are case-insensitive but the comparison was not, soexecutable:notepad.execould not find a process that Windows lists asNotepad.exeโ as it does on Windows 11.handle:matching is numeric and is unchanged. -
RPA.Desktop:
Highlight Elementsnow returns the list of matched element regions instead ofNone, exposing the coordinates that were already being computed internally (#1343, fixes #1324):
- rpaframework now requires
rpaframework-coreโฅ13.0.2, so a fresh install cannot resolve a core version that predates the Windows locator fixes RPA.Windows relies on.
Released packages
- package
rpaframework33.0.1 - package
rpaframework-core13.0.3 - package
rpaframework-pdf11.0.2 - package
rpaframework-recognition8.0.2 - package
rpaframework-google12.0.1 - package
rpaframework-sema4ai1.1.1