security: patch orjson DoS and harden frontend/container security #852
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updating dependencies and hardening components to improve overall security.
I've implemented the following changes:
orjsonto address CVE-2025-67221. I noticed the project was using version 3.10.15, which is vulnerable to recursion-based DoS. Bumping it to >=3.11.5 mitigates this risk.transformPastedHTMLinmessage-input.tsxto useDOMParserinstead ofinnerHTML. This provides a more secure way to strip HTML and prevents potential Self-XSS when pasting content.Dockerfileto use a non-root user. Running the application asappuserfollows container security best practices and limits the attack surface.These modifications ensure the project aligns with modern security standards while maintaining existing functionality. Verified the changes locally with
uv sync.