Skip to main content

CVE-2026-104796chevereto server-side request forgery

Low priorityMedium5.1EPSS not scored yet

CVE-2026-104796 is a server-side request forgery in chevereto, rated medium (5.1 on CVSS 4.0).

Why this priority: Medium severity, with no exploitation signal.

Published · Updated · NVD status: Received

What it is

The server can be made to fetch an address of the attacker's choosing, including internal services and cloud metadata endpoints.

How it is reached

An attacker can exploit it over the network, with an administrator account, and nobody has to click anything.

What an attacker gains

The scored direct impact on the component itself is low. In practice, this kind of flaw lets an attacker make the server send requests into internal networks or cloud metadata. The damage can spread past the vulnerable component into others.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. Upgrade chevereto to 4.5.8 or later.
  2. Until it is patched, review who holds accounts that can reach it.

Description from NVD

Chevereto before 4.5.8 contains a server-side request forgery vulnerability that allows authenticated administrators to cause the server to issue arbitrary requests by supplying a malicious URL to the uploadToWebsite function, which fetches the raw source via fetch_url before the Upload::checkValidUrl SSRF guard can be invoked. Attackers can target loopback addresses, RFC1918 internal services, cloud instance metadata endpoints, and file/gopher/dict schemes through the /json upload action to disclose internal responses or credentials when the fetched content is stored and served back as a public image URL.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Services that fetch URLs or call other hosts for a caller. The flaw sits between the application and the internal network behind it.

Trust boundaries in play

  • Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
  • Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
  • Between the application and the internal network behind it. An attacker who crosses it can make the server send requests into internal networks or cloud metadata.

Questions to answer about your own systems

  • Where does chevereto run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.