Skip to content

[Snyk] Security upgrade react-native from 0.48.4 to 0.69.12 #18

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.

Sign up for GitHub

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

Open
MHxGH-ServiceAccount wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Security upgrade react-native from 0.48.4 to 0.69.12 #18

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion examples/SafariViewExample/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@
},
"dependencies": {
"react": "16.0.0-alpha.12",
"react-native": "0.48.4",
"react-native": "0.69.12",

@cursor cursor Bot Feb 13, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

React Native and React versions are incompatible

Medium Severity

react-native was upgraded to 0.69.12 but react remains 16.0.0-alpha.12. react-native@0.69 expects a React 18 peer, so this dependency set is inconsistent and can break install resolution or runtime behavior in examples/SafariViewExample/package.json.

Additional Locations (1)

Fix in Cursor Fix in Web

@cursor cursor Bot Feb 13, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Start script targets removed React Native CLI

Medium Severity

After upgrading to react-native@0.69.12, the start script still executes node_modules/react-native/local-cli/cli.js. That legacy CLI path is no longer used in newer React Native, so yarn start in examples/SafariViewExample/package.json can fail immediately.

Additional Locations (1)

Fix in Cursor Fix in Web

@cursor cursor Bot Feb 13, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Lockfile still pins old React Native

Medium Severity

package.json now requests react-native@0.69.12, but examples/SafariViewExample/yarn.lock still resolves react-native@0.48.4. In lockfile-driven installs, the vulnerable version can remain in use or installs can fail under frozen lock settings, so the security upgrade is not reliably applied.

Fix in Cursor Fix in Web

"react-native-safari-view": "file:../.."
}
}