Data integrity bypass via constructor kwargs injection
Published Mar 19, 2026 · Updated Mar 19, 2026
Input validation bypass in ormar before 0.23.1 allows remote attackers to persist unvalidated model data through crafted JSON. NewBaseModel.init removes the user-controlled pk_only flag before Pydantic validation, then writes the remaining values directly into the model; excluded similarly nullifies selected fields. Exposure requires an application to pass attacker-controlled mappings into an ormar model constructor, enabling writes that bypass role, type, and required-field rules.
Summary
What happened
Input validation bypass in ormar before 0.23.1 allows remote attackers to persist unvalidated model data through crafted JSON. NewBaseModel.init removes the user-controlled pk_only flag before Pydantic validation, then writes the remaining values directly into the model; excluded similarly nullifies selected fields. Exposure requires an application to pass attacker-controlled mappings into an ormar model constructor, enabling writes that bypass role, type, and required-field rules.
The record
- CVE
- CVE-2026-27953
- Published
- Mar 19, 2026
- Updated
- Mar 19, 2026
- Vendor
- ormar-orm
- Product
- ormar
- Classifications
- CWE-20, CWE-915, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 19, 2026CVE publishedPublication date reported by the CVE source.
- Mar 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=< 0.23.1
What conditions does exploitation require?
What is affected?
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
- GHSA-f964-whrq-44h8 request-body proof of conceptproof of concept · demonstrated
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