Click the green button below to open GitHub’s new-issue form, pre-filled with the
report title, summary table, top findings, and an embedded score-card image.
No authentication needed — you review on GitHub
before submitting. Repobility is credited as the scanner.
Embedded score card image
This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.
Issue title
Unsafe Deserialization
Curate findings to include
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
Top 5 (default)
Issue body (markdown)
## Code-quality scan: `medusajs/medusa`
**Score: 67/100 (B+)** · 59 findings · scanned 2026-05-17 19:53 UTC · 1,019,160 LOC
| Severity | Count |
|---|---|
| CRITICAL | 1 |
| HIGH | 3 |
| MEDIUM | 17 |
| LOW | 38 |
📊 [Full filterable report](https://repobility.com/scan/5f88f9b1-bad0-4cff-861c-da0f06324fff/) · 
### Top findings
1. **CRITICAL** `JRN001` — Token handoff appears to use a callback URL or fragment
`packages/cli/create-medusa-app/src/utils/project-creator/medusa-project-creator.ts:194`
2. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input
`packages/admin/dashboard/src/routes/product-tags/product-tag-list/loader.ts:14` · A10:2021 SSRF
3. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input
`packages/admin/dashboard/src/routes/orders/order-detail/components/order-fulfillment-section/order-fulfillment-section.tsx:419` · A10:2021 SSRF
4. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input
`packages/admin/dashboard/src/components/common/file-upload/file-upload.tsx:88` · A10:2021 SSRF
5. **MEDIUM** `SEC007` — Unsafe Deserialization
`packages/cli/oas/medusa-oas-cli/src/utils/yaml-utils.ts:6` · A08:2021 Software & Data Integrity Failures
---
**Security note**: this issue is public. If any flagged finding is a real, exploitable vulnerability, please redirect to your `SECURITY.md` policy or open a [private security advisory](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability) instead. We're happy to close this and re-submit privately.
---
_Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/5f88f9b1-bad0-4cff-861c-da0f06324fff/_
Already filed
Repobility already filed issue #15418 on this repo on 2026-05-17. Filing again would be duplicate spam.
This scan was submitted by a Enterprise-tier account. Premium accounts have full outreach control â Repobility doesn't pre-fill the 'file as GitHub issue' button for paid users. You can still file the issue manually using the markdown body above (Copy markdown), or contact us if you'd like batch-filing enabled for your account.
Already filed
This repo publishes a SECURITY.md policy and the scan contains 3 Critical/High security finding(s). Public issue filing would violate coordinated disclosure. Submit privately via the project's security reporting channel.
Megaproject â high spam risk
Could not determine 'medusajs/medusa' star count (GitHub API rate-limited or unreachable). When in doubt about repo size, prefer opening a focused PR or a discussion rather than an issue.
The button opens GitHubâs new-issue page in a new tab. You will see the title +
body pre-filled â review, edit if you want, then click GitHubâs "Submit new issue"
button. Repobility never posts anything on your behalf.
For real security findings on big repos: use the project's SECURITY.md or
private advisory flow instead of a public issue.
