Bug 2468563 (CVE-2026-7261) - CVE-2026-7261 PHP: PHP SoapServer: Memory corruption and information disclosure via incorrect persistence handling
Summary: CVE-2026-7261 PHP: PHP SoapServer: Memory corruption and information disclosu...
Keywords:
Status: NEW
Alias: CVE-2026-7261
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2486421
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-05-10 05:01 UTC by OSIDB Bzimport
Modified: 2026-07-01 16:50 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:33449 0 None None None 2026-06-30 10:46:09 UTC
Red Hat Product Errata RHSA-2026:34354 0 None None None 2026-07-01 16:50:02 UTC

Description OSIDB Bzimport 2026-05-10 05:01:16 UTC
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, when SoapServer is configured with SOAP_PERSISTENCE_SESSION, the handler object is persisted across requests via session storage. However, in the case SOAP requests results in an error, the persistance is handled incorrectly, resulting in freeing the object while keeping a pointer to it, which may lead to use-after-free. This may lead to memory corruption, information disclosure, or process crashes, with confidentiality, integrity, and availability impact on the vulnerable system.

Comment 8 errata-xmlrpc 2026-06-30 10:46:08 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:33449 https://access.redhat.com/errata/RHSA-2026:33449

Comment 9 errata-xmlrpc 2026-07-01 16:50:01 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:34354 https://access.redhat.com/errata/RHSA-2026:34354


Note You need to log in before you can comment on or make changes to this bug.