ACVEAgent configuration vulnerability registry

ACVE-2026-0423

Ollama honeypots received sustained enumeration and model probes

In the wild

weaponised-poc · vendor

Description

What

GreyNoise recorded sustained sessions against Ollama honeypots and enumeration of more than 73 LLM endpoints. The observation demonstrates active reconnaissance and feeds the exposed-Ollama incident row; it is not a count of compromised machines or a claim that every request led to model access.

Which configuration is exposed

The exposed configuration is Ollama with OLLAMA_HOST set, making the API potentially reachable beyond loopback. The lock does not know whether a firewall or proxy blocks the service, so the finding is a review signal for a network boundary rather than a live scan result.

How ACVE detects it

ACVE checks the Ollama harness and the environment-presence feature. It records only that the variable was set, not its value. Missing feature data produces possible rather than clean.

Fix

Bind Ollama to loopback, require authentication for intentional remote access, and review request logs for enumeration. Rotate any credentials available to processes that served models on a public endpoint.

Grounding needed

GreyNoise should be checked for the session windows and methodology. The reported session counts remain telemetry and are not converted into victim numbers.

This record is limited to the condition named in the public source: Ollama honeypots received sustained enumeration and model probes. A match is a review signal for that condition, not a claim that every installation, package, model, or host was compromised. Operators should preserve the resolved evidence and investigate adjacent credentials, network exposure, and execution history before closing the finding. The result should be retained with the lock snapshot used for the match so later review can distinguish configuration drift from a changed public record.

Configuration

and
  harness.id eq "ollama"
  features["OLLAMA_HOST.set"] eq true

Fix

Keep Ollama on loopback or behind an authenticated proxy.

  • Reconfigure OLLAMA_HOST to 127.0.0.1. Remove unauthenticated exposure.

Validation

No validation entries recorded.

Grounding

No grounding checks recorded.

References

No references recorded.

Report a problemValidate this advisoryDiscussJSONEdit on GitHub