Skip to main content
VulnerabilityPublished

CVE-2026-130161: alexbates Tamari · Server-Side Request Forgery

Affects alexbates TamariSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.7.2 when convenient.

Data as of 19 Nov 2026, 20:06 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.3
Patch
Available – fixed in 1.7.2
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade alexbates Tamari to 1.7.2.

Affected software

ProductAffectedFixed in
alexbatesTamariAffected
  • <1.7.2
Fixed in
  • 1.7.2

AI-suggested

Upgrade Tamari to version 1.7.2 or later, where the SSRF vulnerability is fixed. No other mitigations are indicated or required according to the vendor advisory.

Description

Tamari, a recipe manager web application built with Python and Flask, has a server-side request forgery (SSRF) vulnerability prior to version 1.7.2. Authenticated users can bypass the SSRF check in the recipe autofill feature by exploiting DNS rebinding, causing the application to fetch data from internal or private addresses despite initial validation. This allows internal service reconnaissance and potential data exposure. The issue is fixed in version 1.7.2.

References

Community reviews

Loading reviews…