Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
AUTOMATICALLY VERIFIEDOFFICIAL VENDOR SOURCECOLLECTED 12 SEP 2026

Influxdata · AUTOMATIC DISCOVERY

Telegraf Lifecycle policy

Telegraf is tracked by BlackTree as a server-side software product. Its lifecycle page separates release identity, maintenance and security boundaries using the publisher's registered source.

Evidence status

This record passed BlackTree's automatic primary-source checks with a confidence score of 82. It is returned for operational research without requiring routine manual approval. Confirm edition and deployment applicability before acting.

Product overview

Telegraf is tracked by BlackTree as a server-side software product. Its lifecycle page separates release identity, maintenance and security boundaries using the publisher's registered source.

Main capabilities

  • Networked or application service delivery
  • Administrative and operational interfaces
  • Versioned maintenance and security updates

Typical use

Used to provide application, infrastructure or operational services to other systems and users.

Deployment

Deployed on servers, virtual machines, containers or managed infrastructure.

This category-level context is generated from the registered product identity. Confirm exact product capabilities on the publisher's page .

Collected lifecycle data

ProductTelegraf
ReleaseLifecycle policy
Start or releaseNot extracted
Lifecycle boundaryContinuous or not dated in the source
Date precisionUnknown

Known exploited vulnerabilities

Catalogue updated 11 Sep 2026

These are product-family matches in the CISA Known Exploited Vulnerabilities catalogue. Confirm the affected product version in the vendor advisory.

No CISA known-exploited entries currently match this mapped product family.

This does not mean the product has no vulnerabilities.

Package vulnerability advisories

OSV advisories are matched through the registered package URL. A package-family match does not prove that the installed release is affected. Check the affected and fixed versions before remediation.

No package advisories have been linked for this product identity.

This is not evidence that the product has no vulnerabilities.

Source evidence

PRIMARYManual

InfluxDB official lifecycle source

Minor Releases (x.Y.z) are vehicles for delivering minor feature developments, enhancements to existing features, and error corrections. They incorporate all applicable error corrections made in prior Minor Releases and Maintenance Releases. | Maintenance Releases (x.y.Z) are vehicles for delivering error corrections that are severely affecting a number of customers and cannot wait for the next Major Release or Minor Release. They incorporate all applicable error corrections made in prior Maintenance Releases. There is no predefined schedule for Maintenance Releases, these are released as needed based on customer feedback and outstanding errors. | Any other fourth digit or beyond numbering may constitute special releases to address specific customer issues and will be delivered by exception only. It is the expectation that any fourth digit releases will be retired in a timely manner by the customer once the issue has been addressed within a standard release. | (b) InfluxData will provide Support Services for the current Minor Release (x.Y) of the Software and the immediately preceding Minor Release (x.Y) of the Software, inclusive of all Maintenance Releases (x.y.Z) included in the respective Minor Release. (By way of example only, InfluxData releases 1.8 (Major release version 1, Minor release version 8) and several maintenance releases thereafter (1.8.1, 1.8.2 and so forth). InfluxData then releases a new Minor Release, 1.9 (Major release version 1, Minor release version 9) and several maintenance releases thereafter (1.9.1, 1.9.2 and so forth). In this example, InfluxData would provide Support Services for 1.8 and 1.9 and all of its respective maintenance releases). | (c) In the event InfluxData releases a Major Release (X.y), InfluxData will provide Support Services for the current Major Release (X.y) of the Software and the immediately preceding Minor Release (x.Y) of the Software, inclusive of all Maintenance Releases (x.y.Z) included in the respective Minor Release for at least 12 months from the InfluxData general availability of the Major Release. (By way of example only, InfluxData releases 2.0 (Major release version 2, Minor release version 0) and several maintenance releases thereafter (2.0.1, 2.0.2 and so forth). In this example, InfluxData would provide Support Services not only for 2.0 and its maintenance releases, but also 1.9 and all of its respective maintenance releases for at least 12 months from the InfluxData general availability of 2.0).

Publisher identity used by product-specific official-source collectors.

First collected 12 Sep 2026 · Last collected 12 Sep 2026 · Review state accepted

Open official vendor source