Skip to main content
Menu
CVEs

Tamari SSRF via DNS rebinding in recipe autofill

CVE-2026-130161EUVD-2026-130689Published November 19, 2026, updated

5.3MediumCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 1.7.2
Who is exposed
Not reported

Summary

Tamari, a recipe manager web application from alexbates, has a flaw in its recipe autofill feature. An attacker with a low-privilege account can use a hostname that resolves to a public address during validation and to an internal address during the actual request, so the server fetches internal addresses the check was meant to block. Remotely, this lets the attacker probe internal services and potentially expose data from the parsed responses.

Written by a model

Original description

Tamari is a fully-featured recipe manager web application built using Python and the Flask Framework. Prior to 1.7.2, an authenticated user can bypass the recipe-autofill SSRF check by submitting a hostname under the user's control through the Autofill from URL feature; the hostname can resolve to a public address during validation and a private or internal address during the later connection. In app/myrecipes/routes.py, is_safe_autofill_url validates the first DNS response, but recipe autofill passes the original URL to requests.get, which independently resolves the hostname and can connect to the internal address. The fetched response is parsed into recipe fields, enabling internal-service reconnaissance and potential data exposure; no redirect is required, and disabling redirects does not stop this DNS-rebinding bypass. This issue is fixed in 1.7.2.

What to do

Upgrade to a fixed version: 1.7.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130161 (Tamari: SSRF via DNS rebinding bypasses is_safe_autofill_url() in recipe autofill), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130161 (entry last updated 2026-11-19):
Affected:
- alexbates Tamari: fixed in 1.7.2
Fixed versions: 1.7.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130161 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130161 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/alexbates/Tamari/security/advisories/GHSA-fj24-576j-7fh7
- https://github.com/alexbates/Tamari/commit/50f69e3e66c0f41aaab013838340dcdb868dd958
- https://github.com/alexbates/Tamari/releases/tag/v1.7.2
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130161
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130161"}.

Affected versions

cve.now Index

23Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.3/10CVSS 5.3
  • No patch0/5No signal

What would change the score

  • Would score about 63 if added to CISA KEV
  • Would score about 58 if CISA's SSVC rates exploitation active
  • Would score about 42 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · alexbates/Tamari · Advisory GHSA-fj24-576j-7fh7
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130161
RecordNVD · CVE-2026-130161
Other links 2
RepositoryGitHub · alexbates/Tamari · Commit 50f69e3e
RepositoryGitHub · alexbates/Tamari · Release v1.7.2

Questions about CVE-2026-130161

Is CVE-2026-130161 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-130161?

Tamari: before 1.7.2.

Source: cve.now feed data

How do I fix CVE-2026-130161?

Upgrade to a fixed version: 1.7.2.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.