Skip to content

CVEs in container image #406

@nissessenap

Description

@nissessenap

Hi

There are currently a number of CVEs in the container and it contains a number of critical ones

I'm assuming these CVEs isn't an issue due to the MCP server don't use SQLlite for exmaple.

To see exactly which CVEs that exist, you can use grype for example
grype grafana/mcp-grafana:0.7.9

The problem is that the image used is very broad.

FROM debian:bullseye-slim@sha256:52927eff8153b563244f98cdc802ba97918afcdf67f9e4867cbf1f7afb3d147b

My suggestion is to either start using KO, just like we do in the grafana-operator.
But I don't know how the general MCP container gets built the same way or not compared to https://hub.docker.com/r/grafana/mcp-grafana
It looks like the mcp-publisher only gets an image

- name: Install dependencies
so we could probably use ko.

Or we just change it to using a small image, like distroless or chainguard (this is what ko does nowadays).

I'm willing to help out with a PR around this, but I don't want to waste my time unless you think it's a good idea.
So please provide some feedback on which way to go.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions