Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-102811 – Unauthenticated Content/Config Manipulation & Path Traversal – Marmite ≤ 0.4.2

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-102811 is a missing-authentication vulnerability (CWE-306) in the Marmite static-site generator’s built-in development server (marmite --serve), affecting all versions through 0.4.2. The server’s /__marmite__/content, /__marmite__/config, and /__marmite__/file/ endpoints accept requests with no credential check, and unsanitized path parameters in the content-creation and content-cloning handlers allow directory traversal, letting an unauthenticated network attacker create, modify, or overwrite files both inside and outside the site’s project directory. The issue is rated HIGH severity (CVSS 8.7 under v4.0 scoring).

Technical details

  • Root cause: The --serve development server exposes management endpoints (/__marmite__/content, /__marmite__/config, /__marmite__/file/) without any authentication, and the handle_create_content and handle_clone_content handlers in src/server.rs do not sanitize user-supplied path/slug parameters before writing files.
  • Trigger conditions: The target must be running Marmite’s development server (marmite --serve), which by default listens on all network interfaces (0.0.0.0:8000) rather than loopback only.
  • Attack vector: Network — no authentication, user interaction, or special privileges are required to send crafted requests to the exposed endpoints.
  • Impact: High integrity impact. An attacker can create, modify, or overwrite site content and configuration, and write files outside the intended project directory via directory traversal (path traversal in slug/clone/move parameters).

Affected software

  • Marmite (Rust crate marmite, maintained by rochacbruno) — all versions through 0.4.2, when run with the --serve development server flag.
  • Static, already-generated site deployments (i.e., not running the dev server) are not affected.

Severity

  • CVSS v3.1: 7.5 (HIGH) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
  • CVSS v4.0: 8.7 (HIGH) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade to a Marmite release containing the fix in commit 303a0bf2fff4302f4164c0c39932fdffc6683ad4, which changes the development server to default to binding on the loopback interface (127.0.0.1) and preserves this behavior even if an explicit bind fails, rather than falling back to all interfaces.
  • If upgrading is not immediately possible:
    • Never expose the marmite --serve development server to the public internet or untrusted networks; restrict it to 127.0.0.1 or a trusted internal network via firewall rules.
    • Place the development server behind a reverse proxy that enforces authentication if remote access is required for legitimate development purposes.
    • Use the development server only for local/offline content authoring, and rely on the statically generated site output for any deployment reachable from the internet.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge