Snapshot 301174

Document
Security page
URL
https://trust.tempo.io/
Fetched
HTTP status
200
Content type
text/html; charset=utf-8
Fetch mode
static
Size
496720 bytes
SHA-256 (raw)
d7a051c4919088f5046fcdc442b7e91f7c273d4d9ba774740a606eeb20ebc586
SHA-256 (normalized text)
1bd455a30aa8532f88b4fba3b0f59583e1bce4027e194c3022767b4570adee5a

Raw (normalized text)

Scripts and page chrome removed; this is what change detection compares.

Java4Shell (CVE-2026-114938): Tempo’s Response
Trust Center
Start your security review
View & download sensitive information
Ask for information
Overview
At Tempo, our strategy, systems, and people work seamlessly together to empower organizations. Our solutions help teams orchestrate the creation and delivery of work, enabling them to focus on their highest priorities and achieve optimal outcomes.
Trust is at the core of everything we do. Our commitment to data privacy and security is embedded in every part of our business. This Trust Center is designed to provide transparency into our security posture and to give you easy access to our compliance documentation, policies, and certifications.
Compliance
ISO/IEC 27001
ISO/IEC 27001 SoA
ISO/IEC 27701
ISO/IEC 27701 SoA
SOC 2 Type 2
GDPR
CCPA
DORA
HIPAA
SOC 1
PCI DSS
CSA STAR Level 1
VPAT
Tempo is reviewed and trusted by
Cisco
Airbus
Netflix
Slack
Oracle
Airbnb
Deloitte
Documents
Featured Documents
REPORTSSOC 2 Report
PRIVACY & DATA PROTECTIONCloud Hosting Locations & Data Residency
COMPLIANCEISO/IEC 27001
DOCUMENTSSecurity & Privacy Whitepapers (In-Depth)
COMPLIANCEISO/IEC 27701
LEGALData Processing Agreement (DPA)
Reports
SOC 2 Report
Penetration Tests
Various Reports
View more
Loop
Application Overview
Loop Compliance Status Letter
Loop Penetration Test
View more
Legal
Data Processing Agreement (DPA)
Privacy Policy
Service-Level Agreement
View more
Product Security
Data Security
SSO Support
Multi-Factor Authentication
Self-Assessments
CAIQ
CAIQ Lite
Privacy & Data Protection
Cloud Hosting Locations & Data Residency
Subprocessors List
Data Breach Notifications
View more
Data Security
Encryption-at-rest
Encryption-in-transit
Physical Security
View more
Risk Profile
Recovery Time Objective24 hours
Recovery Point Objective24 hours
HostingMajor Cloud Provider
App Security
Application Penetration Testing
Credential Management
Secure Development Training
View more
Access Control
Bring Your Own Device (BYOD)
Data Access
Internal Single-Sign-On (SSO)
View more
Policies
Information Security and Privacy Policy
AI Usage Policy
Acceptable Use Policy
View more
Infrastructure
Status Monitoring
Separate Production Environment
BC/DR
View more
Endpoint Security
Disk Encryption
Endpoint Detection & Response
Threat Detection
Corporate Security
Security Operations Center
HR Security
Employee Security and Privacy Awareness Training
View more
Security Grades
Qualys SSL Labs
Strategic Roadmaps
A+
Timesheets, Capacity Planner, Financial Manager
A+
Time Tracker
A+
Structure PPM, Gantt Charts for Structure PPM
A+
Portfolio Manager
A+
Custom Charts
A+
Power BI Connector for Jira
A+
Security Headers
Atlassian
A
Strategic Roadmaps
A
Portfolio Manager
A
Network Security
Firewall
Security Information and Event Management
ESG
Anti-Modern Slavery
Anti-Bribery and Corruption
Diversity, Equity, and Inclusion
View more
BC/DR
Business Continuity Plan (BCP)
Data Backup/Backup Protection
Disaster Recovery Plan (DRP)
View more
Trust Center Updates
Java4Shell (CVE-2026-114938): Tempo’s Response
Vulnerabilities
Status: Mitigations in progress
Impact: No action is needed for Tempo Cloud customers. We have not identified any confirmed exploitation.
Summary
On November 17, 2026, researchers disclosed a critical remote code execution vulnerability in OpenJDK (CVE-2026-114938, “Java4Shell”). It affects multiple Java versions, including Java 17, 21, 25, and 27, across vendor distributions of OpenJDK. Researchers report that exploitation is limited to certain x86-64 processors; ARM64 processors are not affected. Patched runtime versions are not yet available from all vendors.
Tempo’s assessment
Exposure depends on the Java runtime and the processor type a service runs on.
Some Tempo services run on unaffected processors or do not use Java. We are assessing each service individually and applying mitigations where needed.
We have not identified evidence of exploitation and continue to monitor the situation.
Remediation status
Remediation is underway and not yet complete.
In progress: Applying interim mitigations to affected Java services.
In progress: Verifying exposure and the applied fixes across our environment.
Planned: Moving to patched Java runtime versions as vendors release them.
Customer action required
Tempo Cloud: None.
Tempo Data Center apps: these run inside your own Jira or Confluence, on the Java runtime your team manages. Update Java to a patched build from your Java vendor, or apply the vendor’s recommended workaround until one is available.
We will update this post as remediation progresses and when it is complete.
References
Researcher disclosure: calif.io/java4shell
OpenJDK advisory: openjdk.org/groups/vulnerability/advisories/2026-11-17
Oracle Critical Security Patch Update, November 2026: oracle.com/security-alerts/cspunov2026.html
Tempo renews ISO/IEC 27001 and ISO/IEC 27701 certifications, now covering Loop and Workforce Intelligence
Compliance
We’re pleased to share that Tempo has renewed its ISO/IEC 27001:2022 (information security) and ISO/IEC 27701:2019 (privacy information management) certifications for a new three-year cycle, following our September 2026 recertification audit.
What’s new in this cycle
Loop and Workforce Intelligence are now in scope, alongside Timesheets, Tempo Core, Time Tracker, Capacity Planner, Financial Manager, Portfolio Manager, Strategic Roadmaps and Idea Manager, Structure, Gantt Charts for Structure, Custom Charts for Jira and Confluence, and our BI Connectors for Jira (Power BI, Tableau, BigQuery, SQL and Data Studio).
The scope covers Tempo Software Inc and its affiliates for the development, operation, maintenance, and support of our cloud products.
The new certificates are publicly available in the Compliance section of this Trust Center.
eMudhra emSign CA Compromise (CVE-2026-91403): Limited Exposure, No Evidence of Exploitation
Vulnerabilities
Status: Remediation in progress
Impact: Tempo services may be exposed through outbound connections only. We have found no evidence of exploitation.
Summary
On October 21, 2026, eight intermediate certificate authorities operated by eMudhra (emSign) were found to have compromised private keys (CVE-2026-91403). With those keys, an attacker could issue fraudulent TLS certificates for any domain. Major browsers and operating systems have blocked these certificates. Some software runtimes, including Java, Node.js and Go, do not receive these blocks automatically and need updates.
Tempo's assessment
Inbound customer traffic to Tempo is not affected.
Exposure is limited to outbound HTTPS connections that Tempo services make to external hosts.
Exploitation would require an attacker to intercept network traffic between Tempo infrastructure and an external service, and to present a fraudulent certificate.
We have found no evidence of exploitation.
Remediation status
Remediation is underway and not yet complete.
In progress: Blocking the affected intermediate certificates across Tempo services as an interim measure.
In progress: Verifying exposure and the applied fix across our environment.
Planned: Moving to patched runtime versions as vendors make them available.
Planned: Adding build checks to prevent regression.
Customer action required
None.
We will update this post as remediation progresses and when it is complete.
References
OpenJDK vulnerability advisory (CVE-2026-91403)
Node.js October 2026 security releases
Mozilla Bug 2083449
Critical PHP RCE (CVE-2026-109618, CVE-2026-109619): Tempo Not Affected
Vulnerabilities
Impact: Tempo is not affected.
Summary
On October 21, 2026, the PHP project released security fixes for two critical vulnerabilities:
CVE-2026-109618: remote code execution through memory corruption during request cleanup
CVE-2026-109619: remote code execution through stale state reused across requests
Both vulnerabilities allow unauthenticated remote code execution on PHP installations that serve web requests.
Tempo's assessment
Tempo's Security team reviewed our environment and confirmed that PHP is not used in Tempo's production environment, product services or public-facing websites.
Customer action required
None.
References
PHP security advisory
GHSA-w8hw-w9fx-j79w
GHSA-6wmf-4rv5-p3rp
If you need help using this Trust Center, please contact us.
Contact support