CVE-2026-101033
Received Received - Intake

KitchenOwl Household Isolation Bypass via Category ID Exposure

Vulnerability report for CVE-2026-101033, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-27

Last updated on: 2026-09-27

Assigner: VulnCheck

Description

KitchenOwl through 0.7.10 fails to verify that category IDs belong to the caller's household in expense and item operations. Authenticated attackers can enumerate category IDs from other households to read their category names, budgets, and colors, breaking household isolation.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-27
Last Modified
2026-09-27
Generated
2026-09-27
AI Q&A
2026-09-27
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is an Insecure Direct Object Reference (IDOR) vulnerability in KitchenOwl through version 0.7.10. Authenticated attackers can exploit unchecked category IDs in expense and item operations to access data from other households. By enumerating sequential category IDs, attackers can read sensitive information like category names, budgets, and colors belonging to different households, breaking the app's isolation model.

Detection Guidance

To detect this vulnerability, check if your KitchenOwl instance allows unauthorized access to category IDs from other households. Use API requests to test sequential category IDs and verify if non-household data is exposed. Example: Send authenticated requests to /api/categories/{id} with IDs outside your household and check responses for sensitive data like names, budgets, or colors.

Impact Analysis

If you use KitchenOwl, an attacker with access to your account could view financial or household details from other users on the same server. This includes category names that may reveal budgeting habits, colors that could indicate household preferences, and budgets that might expose financial information. The impact depends on the sensitivity of the exposed data in other households.

Compliance Impact

This vulnerability could lead to unauthorized access to personal or financial data across households, violating data isolation principles required by GDPR and HIPAA. Exposure of household budgets or category names may constitute a breach of confidentiality, potentially resulting in regulatory penalties or loss of trust.

Mitigation Strategies

Upgrade KitchenOwl to a version that includes the fix for CVE-2026-101033. If upgrading is not possible, apply the patch manually by ensuring category IDs are validated against household ownership in addItem, updateItem, addExpense, and updateExpense functions. Restrict API access to trusted users and monitor logs for unauthorized category access attempts.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-101033. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart