Skip to content

1019326: Resolved dependabot issues by updating svelte dependency#49

Merged
CCMKarthik123 merged 1 commit intomasterfrom
EJ2-1019326-dep
Apr 8, 2026
Merged

1019326: Resolved dependabot issues by updating svelte dependency#49
CCMKarthik123 merged 1 commit intomasterfrom
EJ2-1019326-dep

Conversation

@BalajiLoganathanSF4826
Copy link
Copy Markdown
Collaborator

Bug description

Dependabot flagged an outdated and vulnerable version of Svelte in package.json.
The existing version (4.2.19) contained security advisories and compatibility warnings. Updating was required to maintain dependency stability and remove security alerts.

Root cause

The project was using an older Svelte (4.2.19) version that Dependabot identified as vulnerable or outdated. This caused dependency mismatch risks, potential security exposure, and triggered automated alerts. The version was not aligned with the recommended patch level for the framework used.

Solution description

Updated Svelte to the latest compatible patch version 5.53.5 as recommended by Dependabot.
This resolves the security alert, ensures dependency consistency, and improves build/runtime stability for the React PDF Viewer examples.

The following issues will be resolved by this change:

medium - Svelte vulnerable to XSS during SSR with contenteditable bind:innerText and bind:textContent
medium - Svelte SSR attribute spreading includes inherited properties from prototype chain
medium - Svelte SSR does not validate dynamic element tag names in ``
medium - Svelte affected by cross-site scripting via spread attributes in Svelte SSR

Copy link
Copy Markdown
Collaborator

@CCMKarthik123 CCMKarthik123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes are fine.

@CCMKarthik123 CCMKarthik123 merged commit c081f43 into master Apr 8, 2026
1 check passed
@CCMKarthik123 CCMKarthik123 deleted the EJ2-1019326-dep branch April 8, 2026 08:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants