EM-20261120-LZVP
VulnerabilityHigh severity
Flyto2 Core Vulnerability (CVE-2026-77313)
CVE-2026-77313
Status
Developing
Since : signals keep joining.
- First Signal
- Nov 19 22:18 UTCC6 NVD CVE API 2.0
- Page Born
- Nov 20 00:09 UTCsecond source joined
- Last Signal
- Nov 20 00:09 UTC28 hours before snapshot
- Sources
- 20 official · 2 research, news or crowd
- Open For
- 21 hoursso far
Life Of This Page
- 1BornA second, independent source names it.
- 2Developing · NowNew signals join; severity can move.
- 3ConfirmedNot yetCISA KEV lists it, or exploitation in the wild is reported.
- 4ResolvedNot yetPast the fix deadline and 14 days with no new signal.
- 5ArchivedNot yet30 days after resolved. Read only; the link keeps working. Reopens if it comes back.
The ID never changes, and earlier addresses keep working. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.
Vulnerability Lifecycle
- Disclosed: reachedNov 19 22:18 UTCC6 NVD published
- Scored: reachedNov 19 22:18 UTCCVSS 7.1 · EPSS 0.3%
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: not yetNot yetNone in sources yet
- Resolved: not yetNot yetAfter 14 quiet days
Timeline
Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.
Signals
- GHSA-pfg2-w999-497v / CVE-2026-77313: Flyto2 Core: SSRF guard validates the resolved IP but connects by hostname, allowing DNS-rebinding TOCTOU (opens source in a new tab) pip:flyto-core High severityDatabaseC26 GitHub Advisory Database
- CVE-2026-77313 (CVSS 7.1) (opens source in a new tab) Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.8, validate_url_ssrf in src/core/utils.py resolves and checks a hostname but returns the hostname URL rather than the validated… High severityDatabaseC6 NVD CVE API 2.0