Skip to content
VulniPulse
Advisory severityHigh8.8Atlassian

High [CVE-2025-22157] Jira Service Management: This High severity PrivEsc (Privilege Escalation) vulnerability was introduced in versions: 9.12.0, 10.3.0, 10.4.0, and 10.5.0…

This high-severity Atlassian advisory covers CVE-2025-22157; related products: Jira Service Management.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2025-22157 Source published Source updated

VulniPulse record published Record updated

CVE-2025-22157
Related products & platforms
AtlassianJira
Open source advisory

Android app · Google Play

Monitor future Atlassian CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

This High severity PrivEsc (Privilege Escalation) vulnerability was introduced in versions:

9.12.0, 10.3.0, 10.4.0, and 10.5.0 of Jira Core Data Center and Server

This PrivEsc (Privilege Escalation) vulnerability, with a CVSS Score of 7.2, allows an attacker to perform actions as a higher-privileged user.

Jira Core Data Center 10.3: Upgrade to a release greater than or equal to 10.3.5

See the release notes.

This vulnerability was reported via our Atlassian (Internal) program.

Affected product named by the advisory: Jira Service Management.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · medium-confidence parse· fetched 3 months ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · medium-confidence parse· fetched 3 months ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · medium-confidence parse· fetched 3 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.