Backend crash via unvalidated rule weight
Published Sep 13, 2026 · Updated Sep 13, 2026
Out-of-bounds reads in PostGIS address_standardizer through 3.7.0 allow attackers to crash PostgreSQL via crafted rule rows. The rule loader uses the caller-controlled Weight field as an index into the load_value array without first enforcing its valid bounds. Exploitation requires control of rows returned by the rules query and invocation of address standardization; the backend crash terminates all cluster sessions.
Summary
What happened
Out-of-bounds reads in PostGIS address_standardizer through 3.7.0 allow attackers to crash PostgreSQL via crafted rule rows. The rule loader uses the caller-controlled Weight field as an index into the load_value array without first enforcing its valid bounds. Exploitation requires control of rows returned by the rules query and invocation of address standardization; the backend crash terminates all cluster sessions.
The record
- CVE
- CVE-2026-90775
- Published
- Sep 13, 2026
- Updated
- Sep 13, 2026
- Vendor
- PostGIS
- Product
- address_standardizer
- Classifications
- T1499.004
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 13, 2026CVE publishedPublication date reported by the CVE source.
- Sep 13, 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=0 <=3.7.0
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
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