Approved changes feed: RSS · Atom
cpe:2.3:a:collerek:ormar:*:*:*:*:*:python:*:*part: a version: * update: *
| Vendor | Collerek (3cfd5470-7ebc-52ee-87ca-a9c47ba18791) |
|---|---|
| Product | Ormar (bc237a1a-e0d6-557c-b435-3a5ea990aa0c) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | python |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-27953 |
vulnerable | 2026-06-08 07:55:14.711914 |
ormar has a Pydantic Validation Bypass via Kwargs Injection in Model Constructor
HIGH (7.1)
ormar is a async mini ORM for Python. Versions 0.23.0 and below are vulnerable to Pydantic validation bypass through the model constructor, allowing any unauthenticated user to skip all field validation by injecting "__pk_only__": true into a JSON request body. By injecting "__pk_only__": true into a JSON request body, an unauthenticated attacker can skip all field validation and persist unvalidated data directly to the database. A secondary __excluded__ parameter injection uses the same pattern to selectively nullify arbitrary model fields (e.g., email or role) during construction. This affects ormar's canonical FastAPI integration pattern recommended in its official documentation, enabling privilege escalation, data integrity violations, and business logic bypass in any application using ormar.Model directly as a request body parameter. This issue has been fixed in version 0.23.1.
Published: 2026-03-19T20:23:06.379Z
Updated: 2026-03-20T18:10:57.521Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-26198 |
vulnerable | 2026-06-08 07:53:21.399008 |
ormar is vulnerable to SQL Injection through aggregate functions min() and max()
CRITICAL (9.8)
Ormar is a async mini ORM for Python. In versions 0.9.9 through 0.22.0, when performing aggregate queries, Ormar ORM constructs SQL expressions by passing user-supplied column names directly into `sqlalchemy.text()` without any validation or sanitization. The `min()` and `max()` methods in the `QuerySet` class accept arbitrary string input as the column parameter. While `sum()` and `avg()` are partially protected by an `is_numeric` type check that rejects non-existent fields, `min()` and `max()` skip this validation entirely. As a result, an attacker-controlled string is embedded as raw SQL inside the aggregate function call. Any unauthorized user can exploit this vulnerability to read the entire database contents, including tables unrelated to the queried model, by injecting a subquery as the column parameter. Version 0.23.0 contains a patch.
Published: 2026-02-24T02:03:47.094Z
Updated: 2026-02-24T20:35:44.673Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.