-
Notifications
You must be signed in to change notification settings - Fork 1.2k
fix: fix security issue #1967
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: fix security issue #1967
Conversation
Please make sure all the checkboxes are checked:
|
|
Caution Review failedThe pull request is closed. WalkthroughThis pull request adds the CBOR2 library (version 5.8.0+) as a project dependency and simplifies the GitHub pull request template by removing certain change type options and acceptance criteria while refocusing the screenshot documentation section. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ❌ 3❌ Failed checks (1 warning, 2 inconclusive)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 📜 Recent review detailsConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Disabled knowledge base sources:
📒 Files selected for processing (1)
Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
pyproject.toml (1)
63-63: Version constraint lacks upper bound; inconsistent with codebase patterns.The version constraint
cbor2>=5.8.0has no upper bound, which deviates from the pattern used for most other dependencies in this file (e.g.,openai>=1.80.1,pydantic>=2.10.5,<2.12.0). An unbounded upper constraint risks compatibility issues from future major releases and makes builds non-deterministic.Consider specifying an upper bound (e.g.,
cbor2>=5.8.0,<6.0.0) to maintain consistency and ensure reproducibility.🔎 Proposed versioning fix
- "cbor2>=5.8.0" + "cbor2>=5.8.0,<6.0.0"
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (1)
uv.lockis excluded by!**/*.lock
📒 Files selected for processing (1)
pyproject.toml
🧰 Additional context used
📓 Path-based instructions (1)
pyproject.toml
📄 CodeRabbit inference engine (AGENTS.md)
Python version requirement: >= 3.10 and < 3.14
Files:
pyproject.toml
🧠 Learnings (1)
📚 Learning: 2025-11-24T16:45:09.996Z
Learnt from: CR
Repo: topoteretes/cognee PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-11-24T16:45:09.996Z
Learning: Applies to pyproject.toml : Python version requirement: >= 3.10 and < 3.14
Applied to files:
pyproject.toml
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (23)
- GitHub Check: End-to-End Tests / Run Telemetry Pipeline Test
- GitHub Check: End-to-End Tests / Test dataset database deletion in Cognee
- GitHub Check: End-to-End Tests / Test Cognify - Edge Centered Payload
- GitHub Check: End-to-End Tests / Test graph edge ingestion
- GitHub Check: End-to-End Tests / Test adding of label for data in Cognee
- GitHub Check: End-to-End Tests / Conversation sessions test (FS)
- GitHub Check: End-to-End Tests / Conversation sessions test (Redis)
- GitHub Check: End-to-End Tests / Test Feedback Enrichment
- GitHub Check: End-to-End Tests / Test dataset database handlers in Cognee
- GitHub Check: End-to-End Tests / Test Entity Extraction
- GitHub Check: End-to-End Tests / Test permissions with different situations in Cognee
- GitHub Check: End-to-End Tests / Test multi tenancy with different situations in Cognee
- GitHub Check: End-to-End Tests / Concurrent Subprocess access test
- GitHub Check: End-to-End Tests / S3 Bucket Test
- GitHub Check: Basic Tests / Run Simple Examples BAML
- GitHub Check: Basic Tests / Run Unit Tests
- GitHub Check: End-to-End Tests / Server Start Test
- GitHub Check: End-to-End Tests / Deduplication Test
- GitHub Check: Basic Tests / Run Simple Examples
- GitHub Check: Basic Tests / Run Integration Tests
- GitHub Check: Cursor Bugbot
- GitHub Check: CLI Tests / CLI Functionality Tests
- GitHub Check: CLI Tests / CLI Integration Tests
🔇 Additional comments (2)
pyproject.toml (2)
63-63: cbor2>=5.8.0 is compatible with the project's Python requirements.cbor2 5.8.0 and later support Python 3.9–3.14, which fully covers the project's required Python range (3.10–3.13). No action needed.
63-63: Thecbor2>=5.8.0dependency addition addresses CVE-2025-68131, a data-leak vulnerability affecting cbor2 versions 3.0.0–5.7.x where reusing a CBORDecoder could leak values marked with the shareable tag to subsequent decodes. Version 5.8.0 fixed this issue and is compatible with the project's Python requirement (>=3.10,<3.14).Likely an incorrect or invalid review comment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🤖 Fix all issues with AI Agents
In @.github/pull_request_template.md:
- Around line 22-23: The PR template currently forces a mandatory screenshot by
the "## Screenshots" section and the "ADD SCREENSHOT OF LOCAL TESTS PASSING"
placeholder; update the template to make screenshots/videos optional or
conditional by changing the heading text to something like "Screenshots/Videos
(if applicable)" and replace the hard requirement text with guidance that
screenshots are optional and only required for visual/UI changes or when test
output is meaningful, or add a short note listing contribution types that do not
need screenshots (documentation, backend/config changes, refactors).
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (1)
.github/pull_request_template.md
🧰 Additional context used
📓 Path-based instructions (1)
.github/**
⚙️ CodeRabbit configuration file
.github/**: * When the project is hosted on GitHub: All GitHub-specific configurations, templates, and tools should be found in the '.github' directory tree.
- 'actionlint' erroneously generates false positives when dealing with GitHub's
${{ ... }}syntax in conditionals.- 'actionlint' erroneously generates incorrect solutions when suggesting the removal of valid
${{ ... }}syntax.
Files:
.github/pull_request_template.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (27)
- GitHub Check: End-to-End Tests / Test Cognify - Edge Centered Payload
- GitHub Check: End-to-End Tests / Test dataset database deletion in Cognee
- GitHub Check: End-to-End Tests / Test multi tenancy with different situations in Cognee
- GitHub Check: End-to-End Tests / Test graph edge ingestion
- GitHub Check: End-to-End Tests / Test Pipeline Caching
- GitHub Check: End-to-End Tests / Conversation sessions test (Redis)
- GitHub Check: End-to-End Tests / Conversation sessions test (FS)
- GitHub Check: End-to-End Tests / Concurrent Subprocess access test
- GitHub Check: End-to-End Tests / Test Feedback Enrichment
- GitHub Check: End-to-End Tests / Test Entity Extraction
- GitHub Check: End-to-End Tests / Test adding of label for data in Cognee
- GitHub Check: End-to-End Tests / Test dataset database handlers in Cognee
- GitHub Check: End-to-End Tests / Server Start Test
- GitHub Check: End-to-End Tests / Test permissions with different situations in Cognee
- GitHub Check: Basic Tests / Run Formatting Check
- GitHub Check: End-to-End Tests / Run Telemetry Test
- GitHub Check: End-to-End Tests / Test using different async databases in parallel in Cognee
- GitHub Check: End-to-End Tests / S3 Bucket Test
- GitHub Check: Basic Tests / Run Integration Tests
- GitHub Check: End-to-End Tests / Deduplication Test
- GitHub Check: Basic Tests / Run Unit Tests
- GitHub Check: Basic Tests / Run Simple Examples BAML
- GitHub Check: End-to-End Tests / Run Telemetry Pipeline Test
- GitHub Check: Basic Tests / Run Simple Examples
- GitHub Check: CLI Tests / CLI Functionality Tests
- GitHub Check: CLI Tests / CLI Integration Tests
- GitHub Check: Cursor Bugbot
🔇 Additional comments (1)
.github/pull_request_template.md (1)
1-38: Clarify the connection between the PR title and template changes.The PR is titled "fix security issue," but the PR template modifications don't appear to address security-related concerns. Please clarify:
- What security issue is being addressed?
- How do the template changes relate to the security fix (and the cbor2 dependency addition)?
- Were these template changes intentional as part of this security fix, or should they be in a separate PR?
This context would help reviewers understand the full scope of changes and verify the appropriateness of the modifications.
| ## Screenshots | ||
| <!-- ADD SCREENSHOT OF LOCAL TESTS PASSING--> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The screenshot requirement may be too strict for certain contribution types.
The change from "Screenshots/Videos (if applicable)" to a mandatory screenshot requirement with "ADD SCREENSHOT OF LOCAL TESTS PASSING" removes flexibility that could be needed for different types of contributions:
- Documentation-only changes may not have automated tests to screenshot
- Infrastructure, configuration, or backend API changes may not have executable test outputs that make sense to visualize
- Some refactoring or dependency updates (like the cbor2 addition in this PR) may not have meaningful test screenshots
Consider either making this section conditional again or clarifying which types of changes require this specific screenshot.
🤖 Prompt for AI Agents
In @.github/pull_request_template.md around lines 22 - 23, The PR template
currently forces a mandatory screenshot by the "## Screenshots" section and the
"ADD SCREENSHOT OF LOCAL TESTS PASSING" placeholder; update the template to make
screenshots/videos optional or conditional by changing the heading text to
something like "Screenshots/Videos (if applicable)" and replace the hard
requirement text with guidance that screenshots are optional and only required
for visual/UI changes or when test output is meaningful, or add a short note
listing contribution types that do not need screenshots (documentation,
backend/config changes, refactors).
|
You have run out of free Bugbot PR reviews for this billing cycle. This will reset on February 6. To receive reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial. |
Description
Fix security issue reported by the user #1950
Acceptance Criteria
Type of Change
Screenshots/Videos (if applicable)
Pre-submission Checklist
DCO Affirmation
I affirm that all code in every commit of this pull request conforms to the terms of the Topoteretes Developer Certificate of Origin.
Note
cbor2>=5.8.0topyproject.toml; updatesuv.lock(including version bump and wheels) to reflect new dependency..github/pull_request_template.md(simplified change types; renamedScreenshotssection to request proof of local tests passing).LiteLLMEmbeddingEngine.pyandget_api_auth_backend.pywith no functional impact.Written by Cursor Bugbot for commit aa4ab1e. This will update automatically on new commits. Configure here.
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.