More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2269242 Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
Use the following template to for the 'fedpkg update' request to submit an update for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get updated when new packages are pushed to stable. ===== # bugfix, security, enhancement, newpackage (required) type=security # low, medium, high, urgent (required) severity=high # testing, stable request=testing # Bug numbers: 1234,9876 bugs=2269242,2269243 # Description of your update notes=Security fix for [PUT CVEs HERE] # Enable request automation based on the stable/unstable karma thresholds autokarma=True stable_karma=3 unstable_karma=-3 # Automatically close bugs when this marked as stable close_bugs=True # Suggest that users restart after update suggest_reboot=False ====== Additionally, you may opt to use the bodhi web interface to submit updates: https://bodhi.fedoraproject.org/updates/new
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
Some notes: EPEL 8 has python3-rpyc-4.1.4-1.el8.noarch.rpm. Updating to 6.0.1 will require publishing a python3-hatchling package for EPEL 8. There appear to be problems with hatchling on EPEL 8. See https://bugzilla.redhat.com/show_bug.cgi?id=2265090. EPEL 9 does not yet have python3-rpyc. Publishing rpyc on that platform would require first updating some dependencies. More notes on that exist here: https://bugzilla.redhat.com/show_bug.cgi?id=2250962. EPEL 10 does not yet have python3-rpyc. I am working on a package, starting with the dependencies. See https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-ee876a6120.