Curated security intelligence

Recent high-impact CVEs worth tracking.

A curated feed of recent high-impact CVEs that matter to SaaS teams, modern web apps, APIs, auth flows, and security-conscious engineering leaders.

Entries tracked

6

Critical CVEs

5

Known exploited

6

Dashboard focus

Known exploitedCVSS 9+Auth / Access controlCloud / edge / API
CRITICAL Known exploited 2026-04-08

CVE-2026-1340 — Ivanti Endpoint Manager Mobile (EPMM)

Ivanti Endpoint Manager Mobile contains a code injection vulnerability that can allow unauthenticated remote code execution.

Why it matters: A network-reachable RCE on a management surface is the kind of issue that can turn into immediate organizational compromise if exposed.

CVSS

9.8

Category

Code injection / RCE

Vendor

Ivanti

KEV added

2026-04-08

CRITICAL Known exploited 2026-04-06

CVE-2026-35616 — Fortinet FortiClient EMS

FortiClient EMS contains an improper access control vulnerability that may allow unauthenticated attackers to execute unauthorized code or commands.

Why it matters: This is directly relevant to BreachFound positioning because access-control failures remain one of the fastest routes from exposure to compromise.

CVSS

9.8

Category

Improper access control

Vendor

Fortinet

KEV added

2026-04-06

CRITICAL Known exploited 2026-03-30

CVE-2026-3055 — Citrix NetScaler ADC / Gateway

Citrix NetScaler ADC and Gateway contain insufficient input validation in SAML IdP configurations leading to exploitable memory corruption.

Why it matters: Identity and edge infrastructure issues create downstream business risk far beyond a single app because they sit in front of user authentication and traffic flows.

CVSS

9.8

Category

Input validation / memory corruption

Vendor

Citrix

KEV added

2026-03-30

CRITICAL Known exploited 2026-03-27

CVE-2025-53521 — F5 BIG-IP APM

Specific malicious traffic against BIG-IP APM can trigger a stack-based buffer overflow and lead to remote code execution.

Why it matters: Anything sitting on the authentication or access layer deserves priority because compromise there can invalidate every downstream control.

CVSS

9.8

Category

Buffer overflow / RCE

Vendor

F5

KEV added

2026-03-27

HIGH Known exploited 2026-03-26

CVE-2026-33634 — Aqua Security Trivy

A malicious Trivy package was published using compromised credentials, creating a serious CI/CD supply-chain exposure for affected users.

Why it matters: Security tool supply-chain compromise is strategically important because the blast radius can extend into build systems, secrets, and production workflows.

CVSS

8.8

Category

Supply chain / malicious package publish

Vendor

Aqua Security

KEV added

2026-03-26

CRITICAL Known exploited 2026-03-25

CVE-2026-33017 — Langflow Langflow

Langflow contains a code injection vulnerability that can allow building public flows without authentication and can lead to unauthenticated remote code execution.

Why it matters: This is a strong reminder that AI workflow platforms still depend on the same fundamentals: auth, exposure control, and safe request handling.

CVSS

9.8

Category

Code injection / unauthenticated API abuse

Vendor

Langflow

KEV added

2026-03-25

How to use this dashboard

  • Track urgent issues that matter to SaaS teams
  • Use security news as a trigger for internal review
  • Identify patterns around auth, edge, and API exposure
  • Move from awareness to product-specific validation with BreachFound

Turn CVE awareness into product-specific validation.

Security news is useful, but the important question is whether similar patterns exist in your own app or API. Use this dashboard as a trigger to review your exposure and start a focused scan.

FAQ

Does this page list every CVE?

No. The dashboard is intentionally curated. It focuses on recent high-impact entries that are more likely to matter to modern product teams rather than publishing a raw undifferentiated feed.

Why are some CVEs marked as known exploited?

Those entries appear in the CISA Known Exploited Vulnerabilities catalog or are otherwise widely reported as exploited in the wild. They deserve higher urgency than a newly published issue with no known exploitation signal.

How should teams use this dashboard?

Treat it as a curated monitoring layer. Use it to spot patterns worth checking in your own stack, then move into a product-specific validation workflow through your internal review process or a focused security scan.