Product overview
Apache Subversion 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
| Product | Apache Subversion |
|---|
| Release | Lifecycle policy |
|---|
| Start or release | Not extracted |
|---|
| Lifecycle boundary | Continuous or not dated in the source |
|---|
| Date precision | Unknown |
|---|
Known exploited vulnerabilities
Catalogue updated 1 Oct 2026These 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
Apache Subversion official lifecycle source
We try to roll releases on Wednesdays. Like most of the other information on this page, the day we roll isn't a hard-and-fast rule, but it is something that has been useful in the past. Rolling mid-week gives us enough time for the release preparation process in the couple of days prior to the release, and some time before the weekend for validation of the release tarballs. The release is finalized and announced as soon after the completion of the validation process as possible. See the documentation of our release process for more information. | Release support period | Starting with 1.15, all release lines are supported for at least 3 years. At least one release line is always supported. | A release line becomes EOL when the following conditions are both met: | It has been supported for at least 3 years. | It has been supported for at least 3 years. | There is a new minor release line with an age of at least 6 months.
Publisher identity used by product-specific official-source collectors.
First collected 12 Sep 2026 · Last collected 28 Sep 2026 · Review state accepted
Open official vendor source ↗