symfony/symfony

Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

https://github.com/symfony/symfony.git · scanned 2026-05-16 12:56 UTC (1 day, 8 hours ago) · 10 languages

63 findings (6 legacy + 57 scanner) 2/10 scanners ran Scanner says 93 (lower by 10)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 day, 11 hours ago · v1 · 62 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

{# ── 2026-05-17 R27 #5: score breakdown panel ────────────────────── Surfaces the score_breakdown JSON that's been silently stored on Repository for months. Turns hidden math into a trust signal. #}

Severity distribution — click a segment to filter

Active filters: source: legacy × excluding tests × Reset all

Scan summary Repository scanned at 93.1/100 with 88.9% coverage. It contains 14603 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 57 findings — concentrated in cicd (21), software (14), frontend (14). Risk profile is high: 0 critical, 1 high, 16 medium. Recommended next step: open the cicd layer findings first — that's where the highest-impact wins live.

Showing 5 of 62 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high Legacy security path_traversal conf 0.80 [SEC013] Path Traversal — User Input in File Path: User-controlled input used in file path without sanitization. Allows reading arbitrary files.

Use os.path.realpath() and verify the path starts with your expected base directory. Use secure_filename() for uploads.

src/Symfony/Component/HttpFoundation/Request.php:1564 path_traversallegacy

high Legacy security path_traversal conf 0.80 [SEC013] Path Traversal — User Input in File Path: User-controlled input used in file path without sanitization. Allows reading arbitrary files.

Use os.path.realpath() and verify the path starts with your expected base directory. Use secure_filename() for uploads.

src/Symfony/Component/Console/Cursor.php:31 path_traversallegacy

high Legacy software ssrf conf 1.00 [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTTP request to a user-controlled URL without allowlist validation. Attackers can probe internal services (169.254.169.254 metadata, internal Kubernetes endpoints, file:// URIs), exfiltrate data, or pivot through your network. SSRF is OWASP A10:2021 and a frequent foothold in cloud breaches.

Validate the URL against an allowlist BEFORE fetching: ALLOWED = {'images.example.com', 'cdn.example.com'} host = urlparse(url).hostname if host not in ALLOWED: abort(400) Or use a server-side proxy (Imgproxy / serve-files-only-from-S3) that isolates outbound network access from the request h…

src/Symfony/Bundle/FrameworkBundle/Command/ConfigDebugCommand.php:287 ssrflegacy

src/Symfony/Bundle/FrameworkBundle/Controller/AbstractController.php:108 ssrflegacy

src/Symfony/Bundle/FrameworkBundle/Controller/ControllerHelper.php:101 ssrflegacy

{# ── 2026-05-17 Round 14: AI-agent bridge footer ────────────────────── Discoverability: the /agents/voting/ guide + MCP manifest exist but aren't linked from anywhere users actually land. Small, opt-in footer. #}

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/2f002ab7-69a0-4f3a-aec7-77bff343c095/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/2f002ab7-69a0-4f3a-aec7-77bff343c095/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.