Rejected namespace use-after-free report
Published Nov 7, 2025 · Updated Nov 7, 2025
Red Hat rejected the reported libxml2 use-after-free after upstream determined that xmlSetTreeDoc behavior was documented and not a flaw. The report claimed that xmlNodeSetDoc changed a moved node's document pointer without rebinding its namespace pointer, leaving the namespace tied to the source document after that document was freed. Because the CNA withdrew the CVE, no affected Red Hat product, supported exploit impact, or detection target remains.
Summary
What happened
Red Hat rejected the reported libxml2 use-after-free after upstream determined that xmlSetTreeDoc behavior was documented and not a flaw. The report claimed that xmlNodeSetDoc changed a moved node's document pointer without rebinding its namespace pointer, leaving the namespace tied to the source document after that document was freed. Because the CNA withdrew the CVE, no affected Red Hat product, supported exploit impact, or detection target remains.
The record
- CVE
- CVE-2025-12863
- Published
- Nov 7, 2025
- Updated
- Nov 7, 2025
- Vendor
- 389 Directory Server
- Product
- Red Hat JBoss Core Services
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 7, 2025CVE publishedPublication date reported by the CVE source.
- Nov 7, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo