Skip to main content
Menu
CVEs

Temenos Application Framework Java arbitrary file read via path traversal in Como log viewer

Only affects Temenos TAFJ R18.SP76.0 with the Como log-viewing web interface. No vendor rating or fixed version is listed in the checked facts.

CVE-2026-132798EUVD-2026-129454GHSA-PW36-H6R2-GGQXPublished November 19, 2026, updated

8.2HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Specific setups only

Summary

Temenos Application Framework Java (TAFJ) has a path traversal flaw in its Como log viewer that lets an attacker read arbitrary files on the system. An attacker can reach it remotely, but only with a high-privilege login, and no user action is needed.

Written by a model

Original description

Improper Limitation of a Pathname to a Restricted Directory in the Como log viewer in Temenos Application Framework Java (TAFJ) R18.SP76.0 allows remote authenticated attackers to read arbitrary files via path traversal

Who should check

Teams running Temenos TAFJ R18.SP76.0 or earlier with the Como log-viewing web interface

“Como log-viewing web interface of Temenos Application Framework Java (TAFJ) R18.SP76.0”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    Temenos TAFJ R18.SP76.0 with the Como log-viewing web interface
  2. Workaround: The checked facts name no fix or workaround. Check the Temenos advisory for guidance on the Como log-viewing interface until a patch is published.

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-132798 (Path traversal in Temenos Application Framework Java), 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-132798 (entry last updated 2026-11-19):
Affected:
- Temenos Temenos Application Framework Java: versions R18.SP76.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Temenos TAFJ R18.SP76.0 with the Como log-viewing web interface (source: https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0049.md)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-132798 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132798 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/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0049.md
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-132798
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-132798"}.

Affected versions

cve.now Index

21Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.2/10CVSS 8.2
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active
  • Would score about 28 if CISA's SSVC rates it automatable

Timeline

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

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

  4. Record last updated

Evidence 3

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-132798
RecordNVD · CVE-2026-132798
Other links 1
RepositoryGitHub · mandiant/Vulnerability-Disclosures · 2026/MNDT-2026-0049.md

Questions about CVE-2026-132798

Is CVE-2026-132798 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. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

An authenticated user of the Como log-viewing web interface can read arbitrary files on the underlying server and view their contents, including configuration and credential files.

Source: github.com

Which versions are affected by CVE-2026-132798?

Temenos Application Framework Java: version R18.SP76.0.

Source: cve.now feed data

Am I affected, and how do I check?

The bug is in the Como log-viewing web interface of Temenos Application Framework Java (TAFJ) R18.SP76.0. To check a deployment, look at the installed TAFJ version and whether the Como log-viewing interface is in use.

Source: github.com

How do I fix CVE-2026-132798?

The checked facts name no fixed version or patch ids, so check the Temenos advisory for the fix before relying on any upgrade target.

Source: github.com

What if there's no patch?

The checked facts name no fix or workaround. Check the Temenos advisory for guidance on the Como log-viewing interface until a patch is published.

Source: github.com

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