Rejected access-control report
Published Feb 19, 2026 · Updated Feb 19, 2026
CVE-2026-25412 no longer identifies a confirmed Advanced iFrame vulnerability because Patchstack rejected the record. The withdrawn description alleged missing authorization through 2025.10, while the vendor separately says its URL cache could be completely filled instead of enforcing a bounded FIFO policy. That cache existed only when “Add iframe URL as param” used hash or hashrewrite, and current sources do not establish the rejected identifier’s impact.
Summary
What happened
CVE-2026-25412 no longer identifies a confirmed Advanced iFrame vulnerability because Patchstack rejected the record. The withdrawn description alleged missing authorization through 2025.10, while the vendor separately says its URL cache could be completely filled instead of enforcing a bounded FIFO policy. That cache existed only when “Add iframe URL as param” used hash or hashrewrite, and current sources do not establish the rejected identifier’s impact.
The record
- CVE
- CVE-2026-25412
- Published
- Feb 19, 2026
- Updated
- Feb 19, 2026
- Vendor
- Advanced iFrame
- Product
- Advanced iFrame
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Feb 19, 2026CVE publishedPublication date reported by the CVE source.
- Feb 19, 2026Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a <=<= 2025.10
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