|
29775
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Upg
Upg
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
For you
For you
Recent
Recent
Starred
Starred
Apps
Apps
More actions for Apps
More actions for Apps
Spaces
Spaces
Create space
Create space
More actions for spaces
More actions for spaces
Recent
Jiminny (New)
Jiminny (New)
Jiminny (New)
Create board
Create board
More actions for Jiminny (New)
More actions for Jiminny (New)
Platform Team
Platform Team
Board actions
Board actions
Capture Team
Capture Team
Board actions
Board actions
Enterprise Stability Issues 🤕
Enterprise Stability Issues 🤕
Board actions
Board actions
Processing Team
Processing Team
Board actions
Board actions
SE Kanban
SE Kanban
Board actions
Board actions
Service-Desk
Service-Desk
More actions for Service-Desk
More actions for Service-Desk
More spaces
More spaces
Filters
Filters
More actions for Filters
More actions for Filters
Dashboards
Dashboards
Create dashboard
Create dashboard
More actions for Dashboards
More actions for Dashboards
Operations
Operations
More actions for Operations
More actions for Operations
Confluence , (opens new window)
Confluence
, (opens new window)
Teams , (opens new window)
Teams
, (opens new window)
open menu
open menu
Customise sidebar
Customise sidebar
Resize side navigation panel
Spaces
Spaces
/
Jiminny (New)
Jiminny (New)
Platform Team
Platform Team
Add people
Add people
Board actions
Board actions
Share
Automation
Give feedback
Give feedback
Enter full screen
Enter full screen
Summary
Summary
Timeline
Timeline
Backlog
Backlog
Active sprints
Active sprints
Calendar
Calendar
Reports
Reports
Testing Board
Testing Board
List
List
Forms
Forms
Components
Components
Development
Development
Code
Code
Security
Security
Releases
Releases
Deployments
Deployments
5 more tabs
More
5
Add to navigation
Results will be filtered below as you type to search or apply filters.
Search on current page
Filter by assignee
Filter assignees by Lukas Kovalik
Filter assignees by Ahmet Katranci
Filter assignees by Aneliya Angelova
Filter assignees by Galya Dimitrova
Filter assignees by George Tulev
Filter assignees by James Graham
+8
+8
Version
Version
Epic
Epic
Type
Type
Label
Label
Quick filters
Quick filters
Backlog insights
Backlog insights
View settings
View settings
More actions
More actions
Select all work items in sprint Platform Sprint 3 Q2
Platform Sprint 3 Q2 29 Apr – 12 May (17 work items)
Collapse
Collapse
Platform Sprint 3 Q2
Platform Sprint 3 Q2
29 Apr – 12 May
(17 work items)
Platform Sprint 3 Q2
17 work items
Not started (leftmost column): 0 of 59 (days)
In progress: 9.5 of 59 (days)
Completed (rightmost column): 49.5 of 59 (days)
Complete sprint
Complete sprint
Platform Sprint 3 Q2 actions
Platform Sprint 3 Q2 actions
- Release AJ Panorama reports to customers who are using Panorama chat - Define the approach for Jiminny MCP Connector
More actions Open workload by assignee summary modal
Open workload by assignee summary modal
JY-20493 Smart Instant Nudge Pre-filtering. Use the enter key to load the work item
JY-20493 Smart Instant Nudge Pre-filtering
JY-20493
Smart Instant Nudge Pre-filtering
Smart Instant Nudge Pre-filtering
COST-EFFECTIVE AND FASTER NUDGES
status
READY TO MERGE
1.5
JY-20372 AI Reports > Empty page design and promotion . Use the enter key to load the work item
JY-20372 AI Reports > Empty page design and promotion
JY-20372
AI Reports > Empty page design and promotion
AI Reports > Empty page design and promotion
AJ REPORTS
status
DEPLOYED
7
JY-20352 Sync opportunities without a local owner (user_id is null). Use the enter key to load the work item
JY-20352 Sync opportunities without a local owner (user_id is null)
JY-20352
Sync opportunities without a local owner (user_id is null)
Sync opportunities without a local owner (user_id is null)
PLATFORM STABILITY
status
DEPLOYED
9
JY-20726 Grok via Azure. Use the enter key to load the work item
JY-20726 Grok via Azure
JY-20726
Grok via Azure
Grok via Azure
MAINTENANCE
status
DEPLOYED
1
JY-20566 AI Review - Q1 - Summary/Action items/Key Points. Use the enter key to load the work item
JY-20566 AI Review - Q1 - Summary/Action items/Key Points
JY-20566
AI Review - Q1 - Summary/Action items/Key Points
AI Review - Q1 - Summary/Action items/Key Points
GROWTH - MAINTAIN OUR COMPETITIVE POSITION
status
DEPLOYED
10
JY-20625 [POC]Jiminny MCP Connector. Use the enter key to load the work item
JY-20625 [POC]Jiminny MCP Connector
JY-20625
[POC]Jiminny MCP Connector
[POC]Jiminny MCP Connector
JIMINNY MCP CONNECTOR
status
DONE
12
JY-20770 Allow users to delete SS and Panorama prompts when those are used in a Report. Use the enter key to load the work item...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
29775
|
|
30263
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Upg
Upg
Create
Create
Rovo Ask Rovo
Ask Rovo
8 Notifications
8 Notifications...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
30263
|
|
30264
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Upg
Upg
Create...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
30264
|
|
30265
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Upg
Upg
Create
Create
Rovo Ask Rovo
Ask Rovo
8 Notifications
8 Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
For you
For you
Recent
Recent
Starred
Starred
Apps
Apps
More actions for Apps
More actions for Apps
Spaces
Spaces
Create space
Create space
More actions for spaces
More actions for spaces
Recent
Jiminny (New)
Jiminny (New)
Jiminny (New)
Create board
Create board
More actions for Jiminny (New)
More actions for Jiminny (New)
Platform Team
Platform Team
Board actions
Board actions
Capture Team
Capture Team
Board actions
Board actions
Enterprise Stability Issues 🤕
Enterprise Stability Issues 🤕
Board actions
Board actions
Processing Team
Processing Team
Board actions
Board actions
SE Kanban
SE Kanban
Board actions
Board actions
Service-Desk
Service-Desk
More actions for Service-Desk
More actions for Service-Desk
More spaces
More spaces
Filters
Filters
More actions for Filters
More actions for Filters
Dashboards
Dashboards
Create dashboard
Create dashboard
More actions for Dashboards
More actions for Dashboards
Operations
Operations
More actions for Operations
More actions for Operations
Confluence , (opens new window)
Confluence
, (opens new window)
Teams , (opens new window)
Teams
, (opens new window)
open menu
open menu
Customise sidebar
Customise sidebar
Resize side navigation panel
Spaces
Spaces
/
Jiminny (New)
Jiminny (New)
Platform Team
Platform Team
Add people
Add people
Board actions
Board actions
Share
Automation
Give feedback
Give feedback
Enter full screen
Enter full screen
Summary
Summary
Timeline
Timeline
Backlog
Backlog
Active sprints
Active sprints
Calendar
Calendar
Reports
Reports
Testing Board
Testing Board
List
List
Forms
Forms
Components
Components
Development
Development
Code
Code
Security
Security
Releases
Releases
Deployments
Deployments
5 more tabs
More
5
Add to navigation
Results will be filtered below as you type to search or apply filters.
Search on current page
Filter by assignee
Filter assignees by Lukas Kovalik
Filter assignees by Ahmet Katranci
Filter assignees by Aneliya Angelova
Filter assignees by Galya Dimitrova
Filter assignees by George Tulev
Filter assignees by James Graham
+8
+8
Version
Version
Epic
Epic
Type
Type
Label
Label
Quick filters
Quick filters
Backlog insights
Backlog insights
View settings
View settings
More actions
More actions
Select all work items in sprint Platform Sprint 4 Q2
Platform Sprint 4 Q2 12 May – 26 May (15 work items)
Collapse
Collapse
Platform Sprint 4 Q2
Platform Sprint 4 Q2
12 May – 26 May
(15 work items)
Platform Sprint 4 Q2
15 work items
Not started (leftmost column): 43.5 of 47 (days)
In progress: 3.5 of 47 (days)
Completed (rightmost column): 0 of 47 (days)
Start sprint
Start sprint
Platform Sprint 4 Q2 actions
Platform Sprint 4 Q2 actions
More actions Open workload by assignee summary modal
Open workload by assignee summary modal
JY-20361 AJ Panorama for Call Scoring in OD. Use the enter key to load the work item
JY-20361 AJ Panorama for Call Scoring in OD
JY-20361
AJ Panorama for Call Scoring in OD
AJ Panorama for Call Scoring in OD
AUTOMATED AI SCORING
status
IN QA
0.5
JY-20725 [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts. Use the enter key to load the work item
JY-20725 [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts
JY-20725
[HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts
[HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts
PLATFORM STABILITY
status
READY FOR QA
1.5
JY-18091 Upgrade to PHP 8.5. Use the enter key to load the work item
JY-18091 Upgrade to PHP 8.5
JY-18091
Upgrade to PHP 8.5
Upgrade to PHP 8.5
PHP 8.5 UPGRADE
status
IN DEV
1.5
JY-20846 MCP > Enable the AI to know details about the user. Use the enter key to load the work item
JY-20846 MCP > Enable the AI to know details about the user
JY-20846
MCP > Enable the AI to know details about the user
MCP > Enable the AI to know details about the user
JIMINNY MCP CONNECTOR
status
BACKLOG
1.5
JY-20833 MCP > Enable users to get a list of calls and their details. Use the enter key to load the work item
JY-20833 MCP > Enable users to get a list of calls and their details
JY-20833
MCP > Enable users to get a list of calls and their details
MCP > Enable users to get a list of calls and their details
MCP > Enable users to get a list of calls and their details
Jiminny MCP Connector
JIMINNY MCP CONNECTOR
Backlog - Change status
BACKLOG
Edit story point estimate, edit
9
Priority: Medium
Assignee: Nikolay Nikolov
More actions for JY-20833 MCP > Enable users to get a list of calls and their details
More actions for JY-20833 MCP > Enable users to get a list of calls and their details
JY-20835 MCP > Enable users to get a list of deals and their details. Use the enter key to load the work item
JY-20835 MCP > Enable users to get a list of deals and their details
JY-20835
MCP > Enable users to get a list of deals and their details
MCP > Enable users to get a list of deals and their details
MCP > Enable users to get a list of deals and their details
Jiminny MCP Connector
JIMINNY MCP CONNECTOR
Backlog - Change status
BACKLOG
Edit story point estimate, edit
20
Priority: Medium
Assignee: Nikolay Ivanov
More actions for JY-20835 MCP > Enable users to get a list of deals and their details
More actions for JY-20835 MCP > Enable users to get a list of deals and their details
JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report. Use the enter key to load the work item
JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report
JY-20676
Notify the user if a Panorama prompts is deleted but is used in AJ Report
Notify the user if a Panorama prompts is deleted but is used in AJ Report
Notify the user if a Panorama prompts is deleted but is used in AJ Report
AJ Reports
AJ REPORTS
Backlog - Change status
BACKLOG
Edit story point estimate, edit
3
Priority: Medium
Assignee: Lukas Kovalik
More actions for JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report
More actions for JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report
JY-20615 Notify the user if a SS is deleted but is used in AJ Report. Use the enter key to load the work item
JY-20615 Notify the user if a SS is deleted but is used in AJ Report
JY-20615
Notify the user if a SS is deleted but is used in AJ Report...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
30265
|
|
30266
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Upg
Upg
Create
Create
Rovo Ask Rovo
Ask Rovo
8 Notifications
8 Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
For you
For you
Recent
Recent
Starred
Starred
Apps
Apps
More actions for Apps
More actions for Apps
Spaces
Spaces
Create space
Create space
More actions for spaces
More actions for spaces
Recent
Jiminny (New)
Jiminny (New)
Jiminny (New)
Create board
Create board
More actions for Jiminny (New)
More actions for Jiminny (New)
Platform Team
Platform Team
Board actions
Board actions
Capture Team
Capture Team
Board actions
Board actions
Enterprise Stability Issues 🤕
Enterprise Stability Issues 🤕
Board actions
Board actions
Processing Team
Processing Team
Board actions
Board actions
SE Kanban
SE Kanban
Board actions
Board actions
Service-Desk
Service-Desk
More actions for Service-Desk
More actions for Service-Desk
More spaces
More spaces
Filters
Filters
More actions for Filters
More actions for Filters
Dashboards
Dashboards
Create dashboard
Create dashboard
More actions for Dashboards
More actions for Dashboards
Operations
Operations
More actions for Operations
More actions for Operations
Confluence , (opens new window)
Confluence
, (opens new window)
Teams , (opens new window)
Teams
, (opens new window)
open menu
open menu
Customise sidebar
Customise sidebar
Resize side navigation panel
Spaces
Spaces
/
Jiminny (New)
Jiminny (New)
Platform Team
Platform Team
Add people
Add people
Board actions
Board actions
Share
Automation
Give feedback
Give feedback
Enter full screen
Enter full screen
Summary
Summary
Timeline
Timeline
Backlog
Backlog
Active sprints
Active sprints
Calendar
Calendar
Reports
Reports
Testing Board
Testing Board
List
List
Forms
Forms
Components
Components
Development
Development
Code
Code
Security
Security
Releases
Releases
Deployments
Deployments
5 more tabs
More
5
Add to navigation
Results will be filtered below as you type to search or apply filters.
Search on current page
Filter by assignee
Filter assignees by Lukas Kovalik
Filter assignees by Ahmet Katranci
Filter assignees by Aneliya Angelova
Filter assignees by Galya Dimitrova
Filter assignees by George Tulev
Filter assignees by James Graham
+8
+8
Version
Version
Epic
Epic
Type
Type
Label
Label
Quick filters
Quick filters
Backlog insights
Backlog insights
View settings
View settings
More actions
More actions
Select all work items in sprint Platform Sprint 4 Q2
Platform Sprint 4 Q2 12 May – 26 May (15 work items)
Collapse
Collapse
Platform Sprint 4 Q2
Platform Sprint 4 Q2
12 May – 26 May
(15 work items)
Platform Sprint 4 Q2
15 work items
Not started (leftmost column): 43.5 of 47 (days)
In progress: 3.5 of 47 (days)
Completed (rightmost column): 0 of 47 (days)
Start sprint
Start sprint
Platform Sprint 4 Q2 actions
Platform Sprint 4 Q2 actions
More actions Open workload by assignee summary modal
Open workload by assignee summary modal
JY-20361 AJ Panorama for Call Scoring in OD. Use the enter key to load the work item
JY-20361 AJ Panorama for Call Scoring in OD
JY-20361
AJ Panorama for Call Scoring in OD
AJ Panorama for Call Scoring in OD
AUTOMATED AI SCORING
status
IN QA
0.5
JY-20725 [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts. Use the enter key to load the work item
JY-20725 [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts
JY-20725
[HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts
[HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts
PLATFORM STABILITY
status
READY FOR QA
1.5
JY-18091 Upgrade to PHP 8.5. Use the enter key to load the work item
JY-18091 Upgrade to PHP 8.5
JY-18091
Upgrade to PHP 8.5
Upgrade to PHP 8.5
PHP 8.5 UPGRADE
status
IN DEV
1.5
JY-20846 MCP > Enable the AI to know details about the user. Use the enter key to load the work item
JY-20846 MCP > Enable the AI to know details about the user
JY-20846
MCP > Enable the AI to know details about the user
MCP > Enable the AI to know details about the user
JIMINNY MCP CONNECTOR
status
BACKLOG
1.5
JY-20833 MCP > Enable users to get a list of calls and their details. Use the enter key to load the work item
JY-20833 MCP > Enable users to get a list of calls and their details
JY-20833
MCP > Enable users to get a list of calls and their details
MCP > Enable users to get a list of calls and their details
MCP > Enable users to get a list of calls and their details
Jiminny MCP Connector
JIMINNY MCP CONNECTOR
Backlog - Change status
BACKLOG
Edit story point estimate, edit
9
Priority: Medium
Assignee: Nikolay Nikolov
More actions for JY-20833 MCP > Enable users to get a list of calls and their details
More actions for JY-20833 MCP > Enable users to get a list of calls and their details
JY-20835 MCP > Enable users to get a list of deals and their details. Use the enter key to load the work item
JY-20835 MCP > Enable users to get a list of deals and their details
JY-20835
MCP > Enable users to get a list of deals and their details
MCP > Enable users to get a list of deals and their details
MCP > Enable users to get a list of deals and their details
Jiminny MCP Connector
JIMINNY MCP CONNECTOR
Backlog - Change status
BACKLOG
Edit story point estimate, edit
20
Priority: Medium
Assignee: Nikolay Ivanov
More actions for JY-20835 MCP > Enable users to get a list of deals and their details
More actions for JY-20835 MCP > Enable users to get a list of deals and their details
JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report. Use the enter key to load the work item
JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report
JY-20676
Notify the user if a Panorama prompts is deleted but is used in AJ Report
Notify the user if a Panorama prompts is deleted but is used in AJ Report
Notify the user if a Panorama prompts is deleted but is used in AJ Report
AJ Reports
AJ REPORTS
Backlog - Change status
BACKLOG
Edit story point estimate, edit
3
Priority: Medium
Assignee: Lukas Kovalik
More actions for JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report
More actions for JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report
JY-20615 Notify the user if a SS is deleted but is used in AJ Report. Use the enter key to load the work item
JY-20615 Notify the user if a SS is deleted but is used in AJ Report
JY-20615
Notify the user if a SS is deleted but is used in AJ Report
Notify the user if a SS is deleted but is used in AJ Report
Notify the user if a SS is deleted but is used in AJ Report
AJ Reports
AJ REPORTS
Backlog - Change status
BACKLOG
Edit story point estimate, edit...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
30266
|
|
30267
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Upg
Upg
Create
Create
Rovo Ask Rovo
Ask Rovo
8 Notifications
8 Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
For you
For you
Recent
Recent
Starred
Starred
Apps
Apps
More actions for Apps
More actions for Apps
Spaces
Spaces
Create space
Create space
More actions for spaces
More actions for spaces
Recent
Jiminny (New)
Jiminny (New)
Jiminny (New)
Create board
Create board
More actions for Jiminny (New)
More actions for Jiminny (New)
Platform Team
Platform Team
Board actions
Board actions
Capture Team
Capture Team
Board actions
Board actions
Enterprise Stability Issues 🤕
Enterprise Stability Issues 🤕
Board actions
Board actions
Processing Team
Processing Team
Board actions
Board actions
SE Kanban
SE Kanban
Board actions
Board actions
Service-Desk
Service-Desk
More actions for Service-Desk
More actions for Service-Desk
More spaces
More spaces
Filters
Filters
More actions for Filters
More actions for Filters
Dashboards
Dashboards
Create dashboard
Create dashboard
More actions for Dashboards
More actions for Dashboards
Operations
Operations
More actions for Operations
More actions for Operations
Confluence , (opens new window)
Confluence
, (opens new window)
Teams , (opens new window)
Teams
, (opens new window)
open menu
open menu
Customise sidebar
Customise sidebar
Resize side navigation panel
Spaces
Spaces
/
Jiminny (New)
Jiminny (New)
Platform Team
Platform Team
Add people
Add people
Board actions
Board actions
Share
Automation
Give feedback
Give feedback
Enter full screen
Enter full screen
Summary
Summary
Timeline
Timeline
Backlog
Backlog
Active sprints
Active sprints
Calendar
Calendar
Reports
Reports
Testing Board
Testing Board
List
List
Forms
Forms
Components
Components
Development
Development
Code
Code
Security
Security
Releases
Releases
Deployments
Deployments
5 more tabs
More
5
Add to navigation
Results will be filtered below as you type to search or apply filters.
Search on current page
Filter by assignee
Filter assignees by Lukas Kovalik
Filter assignees by Ahmet Katranci
Filter assignees by Aneliya Angelova
Filter assignees by Galya Dimitrova
Filter assignees by George Tulev
Filter assignees by James Graham
+8
+8
Version
Version
Epic
Epic
Type
Type
Label
Label
Quick filters
Quick filters
Backlog insights
Backlog insights
View settings
View settings
More actions
More actions
Select all work items in sprint Platform Sprint 4 Q2
Platform Sprint 4 Q2 12 May – 26 May (15 work items)
Collapse
Collapse
Platform Sprint 4 Q2
Platform Sprint 4 Q2
12 May – 26 May
(15 work items)
Platform Sprint 4 Q2
15 work items
Not started (leftmost column): 43.5 of 47 (days)
In progress: 3.5 of 47 (days)
Completed (rightmost column): 0 of 47 (days)
Start sprint
Start sprint
Platform Sprint 4 Q2 actions
Platform Sprint 4 Q2 actions
More actions Open workload by assignee summary modal
Open workload by assignee summary modal
JY-20361 AJ Panorama for Call Scoring in OD. Use the enter key to load the work item
JY-20361 AJ Panorama for Call Scoring in OD
JY-20361
AJ Panorama for Call Scoring in OD
AJ Panorama for Call Scoring in OD
AUTOMATED AI SCORING
status
IN QA
0.5
JY-20725 [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts. Use the enter key to load the work item
JY-20725 [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts
JY-20725
[HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts
[HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts
PLATFORM STABILITY
status
READY FOR QA
1.5
JY-18091 Upgrade to PHP 8.5. Use the enter key to load the work item
JY-18091 Upgrade to PHP 8.5
JY-18091
Upgrade to PHP 8.5
Upgrade to PHP 8.5
PHP 8.5 UPGRADE
status
IN DEV
1.5
JY-20846 MCP > Enable the AI to know details about the user. Use the enter key to load the work item
JY-20846 MCP > Enable the AI to know details about the user
JY-20846
MCP > Enable the AI to know details about the user
MCP > Enable the AI to know details about the user
JIMINNY MCP CONNECTOR
status
BACKLOG
1.5
JY-20833 MCP > Enable users to get a list of calls and their details. Use the enter key to load the work item
JY-20833 MCP > Enable users to get a list of calls and their details
JY-20833
MCP > Enable users to get a list of calls and their details
MCP > Enable users to get a list of calls and their details
MCP > Enable users to get a list of calls and their details
Jiminny MCP Connector
JIMINNY MCP CONNECTOR
Backlog - Change status
BACKLOG
Edit story point estimate, edit
9
Priority: Medium
Assignee: Nikolay Nikolov
More actions for JY-20833 MCP > Enable users to get a list of calls and their details
More actions for JY-20833 MCP > Enable users to get a list of calls and their details
JY-20835 MCP > Enable users to get a list of deals and their details. Use the enter key to load the work item
JY-20835 MCP > Enable users to get a list of deals and their details
JY-20835
MCP > Enable users to get a list of deals and their details
MCP > Enable users to get a list of deals and their details
MCP > Enable users to get a list of deals and their details
Jiminny MCP Connector
JIMINNY MCP CONNECTOR
Backlog - Change status
BACKLOG
Edit story point estimate, edit
20
Priority: Medium
Assignee: Nikolay Ivanov
More actions for JY-20835 MCP > Enable users to get a list of deals and their details
More actions for JY-20835 MCP > Enable users to get a list of deals and their details
JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report. Use the enter key to load the work item
JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report
JY-20676
Notify the user if a Panorama prompts is deleted but is used in AJ Report
Notify the user if a Panorama prompts is deleted but is used in AJ Report
Notify the user if a Panorama prompts is deleted but is used in AJ Report
AJ Reports
AJ REPORTS
Backlog - Change status
BACKLOG
Edit story point estimate, edit
3
Priority: Medium
Assignee: Lukas Kovalik
More actions for JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report
More actions for JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report
JY-20615 Notify the user if a SS is deleted but is used in AJ Report. Use the enter key to load the work item
JY-20615 Notify the user if a SS is deleted but is used in AJ Report
JY-20615
Notify the user if a SS is deleted but is used in AJ Report
Notify the user if a SS is deleted but is used in AJ Report
Notify the user if a SS is deleted but is used in AJ Report
AJ Reports
AJ REPORTS
Backlog - Change status
BACKLOG
Edit story point estimate, edit
2.5
Priority: Medium
Assignee: Lukas Kovalik
More actions for JY-20615 Notify the user if a SS is deleted but is used in AJ Report
More actions for JY-20615 Notify the user if a SS is deleted but is used in AJ Report
JY-19958 Upgrade BE libraries - May. Use the enter key to load the work item
JY-19958 Upgrade BE libraries - May
JY-19958
Upgrade BE libraries - May...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
30267
|
|
30279
|
HomeActivityFilesLaterMoreSlackcalJiminny…..# engi HomeActivityFilesLaterMoreSlackcalJiminny…..# engineering# general# jiminny-bg# platform-tickets# product launches# random# releases# sofia-office# support# thank-yous# the_people_of jimi...Direct messages. Stoyan TanevP. Galya Dimitrova E. Steliyan Georgiev -e Petko Kashinskifº. Aneliya AngelovaFa. Stefka Stoyanova€. Vasil Vasilev E. Nikolay Ivanov3 Aneliya Angelova, ...Lukas Koval...#:AppsG Jira Cloud® Toast@ Google Cale...MistonWindowHelpQ Describe what you are looking forToastHomeMessagesAboutmerged by you arter approval by @ vasil vasilevTodavvToast APP 10:00 AMReview#12059 Jy 20820 esreindex stream modelhydration4 days old • 12 fileschanged • @Vasil VasilevAdded bv Toast for GitHubMergeapp#12066JY-20725 add HSrate limit handling onachvines rematching1 day old • 12 fileschangedAdded by Toast for GitHubResolve Conflictsapp#11443 Test hubletsatency5 months old - 20 fileschangedMessage Toast+ Aa €D System Audio (output)_2026-05-11_08-21-10.mp4al MacRook Dro Micronhone finnut) 2026-05-11 08-20-59 mn/D System Audio (output)_2026-05-11_08-20-48.mp4• MacBook Pro Microphone (input)_2026-05-11_08-20-28.mp4@1 Svstem Audio (outout) 2026-05-11 08.20-26.mn4D MacBook Pro Microphone (input)_2026-05-11_08-19-58.mp4• System Audio (output)_2026-05-11_08-20-03.mp40 Svstem Audio (outout) 2026-05-11 08-19-41.mo4)• MacBook Pro Microphone (input) 2026-05-11_ 08-19-28.mp4System Audio (output)_2026-05-11_08-19-19.mp4MacBook Pro Microphone (input)_2026-05-11_08-18-58.mp4•1 Svstem Audio (outnut) 2026-05-11 08-18-57 mn/MacBook Pro Microphone (input)_2026-05-11_08-18-29.mp4• Svstem Audio (outout) 2026-05-11 08-18-13.mo4• MacBook Pro Microphone (input)_2026-05-11_08-17-59.mp4Platform Team - Backlog - Jira X[JY-20773] User Pilot not receivinJY-19957 | Remove abanded symp8 Proiect Phoenix - FigmaTypeError: LeaguelFlysystemf|files)e New Tab1L Useroilot | Ask liminny Report Ger- New TabO JIMINNYg For you© Recent# Starred8f AppsQ Spaces@ Jiminny (New)ID Platform TeamIID Capture TeamI Enterprise Stability I...uu Processina leamMl SE Kanbanl(Q Service-Desk= More spaces— FiltersC Dashboards@ Operations2 Confluence:: Teams" Customise sidebar1ny.aulasslan.neuifa/sortwareQ UpgSpaces / Jiminny (New)Platform Team P+® Summary& TimelineE BacklogII Active sprints# Calendar• Search backlog010080+8Version VEpic v• v Plattorm Sprint 4 02 12 Mav - 26 Mav (15 work items)80001.# JY-20361 AJ Panorama for Call Scoring in ODFJY-20/25 Huosootl Ootimise CRM rematchina on delete nuosoot accounts/contactsiV JY-18091 Upgrade to PHP 8.5[ JY-20846 MCP > Enable the Al to know details about the user[ JY-20833 MCP > Enable users to get a list of calls and their details@ JY-20835 MCP > Enable users to get a list of deals and their details• JY-20676 Notifv the user if a Panorama promots is deleted but is used in AJ ReportI… Jy-20615 Notitv the user it a Ss is deleted but is used in AJ Revort@ JY-19958 Upgrade BE libraries - MayQ JY-20613 Allow owner's role to be selected when setting up a trial@ JY-20880 [Deadline 25 May] Migrate depricated Gemini 3.1 Flash Lite Preview modelE JY-19951 Setup test coverage for Prophet in SonarA JY-20410 Improve Activity Type suggestions© JY-20881 Upgrade Python and libraries - MayV JY-20272 [Deadline 17 June] Migrate depricated Gemini models+ Create• v Platform Sprint 5 Q2 26 May - 9 Jun (19 work items)-...N JY-20834 MCP > Authenticate each user for easy access@ JY-20836 MCP > Audit log$0| (Platform] Planning... 21 m left100% Lz8• Wed 13 May 10:40:00+ CreateAsk RovoReports4 Testing Board# ListE Forms e Components ⅘ Development % Code Security & Releases A) DeploymentsMore 5TypevLabel vQuick filters v43.5 [3.5 0Start sprinti0.5|k''AUTOMATED AI SCOR.. IN QAVPLATFORM STABILITYREADY FOR CAVPHP 8.5 UPGRADEIN DEV VBACKLOGVLITMINNY MCP CONN.RACKIOG VJIMINNY MCP CONN...BACKLOGVAJ REPORTSBACKLOGAJ REPORTSBACKLOG VBACKLOGVBACKLOG VMAINTENANCEBACKLOGVMAINTENANCEBACKLOGAUTO-DETECTED AC...BACKLOGMAINTENANCEBACKLOGBACKLOG V15 work items | Estimate: 4745.5 0 0LITMINNY MCP CONN…..RACKIOG VLITMTNNY MCP CONN...BACKLOG...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
30279
|
|
32378
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32378
|
|
32379
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension....
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32379
|
|
32380
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export
Copy
Show more options
Show the uploaded image in a lightbox
Copy prompt
Edit
You said I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
You said
I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
Expand
Assessing the Vulnerability
Gemini said
Gemini said
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Stop response
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Panel
Panel
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Upg
Upg
Clear search
Clear search
More filters
App
App
Jira filter Space
Space
Jira filter Assignee
Assignee
Recent search Upg Recent search
Upg
Recent search
RECENT
RECENT
Work item icon JY-2498: [PHP 8.2 Upgrade] Upgrade dependencies in composer.json to support PHP 8.x Jira • Technical Story • Jiminny (New) You viewed on 09 Mar 2026
JY-2498: [PHP 8.2
Upg
rade]
Upg...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32380
|
|
32384
|
[JY-19965] Upgrade BE libraries - Dec - Jira
[JY-1 [JY-19965] Upgrade BE libraries - Dec - Jira
[JY-19965] Upgrade BE libraries - Dec - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:...
|
Firefox
|
[JY-19965] Upgrade BE libraries - Dec - Jira — Wor [JY-19965] Upgrade BE libraries - Dec - Jira — Work...
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32384
|
|
32385
|
[JY-19965] Upgrade BE libraries - Dec - Jira
[JY-1 [JY-19965] Upgrade BE libraries - Dec - Jira
[JY-19965] Upgrade BE libraries - Dec - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:...
|
Firefox
|
[JY-19965] Upgrade BE libraries - Dec - Jira — Wor [JY-19965] Upgrade BE libraries - Dec - Jira — Work...
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32385
|
|
32386
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export
Copy
Show more options
Show the uploaded image in a lightbox
Copy prompt
Edit
You said I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
You said
I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
Expand
Listen
Show thinking
Gemini said
Gemini said
It makes complete sense why you are confused! You were assigned a task to fix "Backend (BE) vulnerabilities" in your Laravel app, but the screenshot you provided is actually flagging a
JavaScript/Node.js vulnerability
, not a PHP one.
The image shows an alert for
npm-elliptic <= 6.6.1
, which is an
npm
(Node Package Manager) dependency. In modern Laravel applications,
npm
is typically used to manage frontend assets and build tools (like Vite or Laravel Mix), rather than backend PHP code (which uses Composer).
Here is exactly what you need to do to resolve this issue in your project:
1. Locate the Repository
1. Locate the Repository
The Vanta dashboard indicates this vulnerability is in a repository or project named
extension-app
. You need to open your terminal and navigate to the root directory of this specific project where the
package.json
file lives.
2. Identify How the Package is Used
2. Identify How the Package is Used
The package
elliptic
might be something your team installed directly, or (more likely) it is a "transitive dependency"—meaning another package you use relies on it.
Run this command in your terminal to see how it's being required:
Bash
Download code
Copy code
npm ls elliptic
This will output a tree showing exactly which package is bringing in the vulnerable version of
elliptic
.
3. Update the Vulnerable Package
3. Update the Vulnerable Package
You need to update
elliptic
to a version higher than
6.6.1
. You have a few options to do this:
Option A: The Automated Fix (Recommended First Step)
Run the built-in npm audit tool to automatically apply non-breaking updates:
Bash
Download code
Copy code
npm audit fix
Option B: Manual Update
If
elliptic
is a direct dependency in your
package.json
, run:
Bash
Download code
Copy code
npm update elliptic
Option C: Overriding a Transitive Dependency
If
npm audit fix
doesn't work because
elliptic
is deeply nested inside another package that hasn't updated its own dependencies, you can force a newer version by adding an
overrides
section to your
package.json
file:
JSON
Download code
Copy code
{
"dependencies"
: {
// your normal dependencies
},
"overrides"
: {
"elliptic"
:
"^6.6.2"
}
}
After adding that, run
npm install
to regenerate your
package-lock.json
.
4. Commit and Push
4. Commit and Push
Once you have updated the package, verify that your frontend assets still compile successfully (e.g., by running
npm run build
or
npm run dev
).
If everything works, commit the updated
package.json
and
package-lock.json
files and push them to your GitHub repository.
GitHub's Dependabot will automatically detect that the vulnerable version has been replaced and will mark the alert as resolved. Vanta will then sync with GitHub and clear the failing test from your dashboard!
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Panel
Panel
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Upg
Upg
Create
Create
Rovo Ask Rovo
Ask Rovo
8 Notifications
8 Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
For you
For you
Recent
Recent
Starred
Starred
Apps
Apps
More actions for Apps
More actions for Apps
Spaces
Spaces
Create space
Create space
More actions for spaces
More actions for spaces
Recent
Jiminny (New)
Jiminny (New)
Jiminny (New)
Create board
Create board
More actions for Jiminny (New)
More actions for Jiminny (New)
Platform Team
Platform Team
Board actions
Board actions
Capture Team
Capture Team
Board actions
Board actions
Enterprise Stability Issues 🤕
Enterprise Stability Issues 🤕
Board actions
Board actions
Processing Team...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32386
|
|
32387
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export
Copy
Show more options
Show the uploaded image in a lightbox
Copy prompt
Edit
You said I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
You said
I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
Expand
Listen
Show thinking
Gemini said
Gemini said
It makes complete sense why you are confused! You were assigned a task to fix "Backend (BE) vulnerabilities" in your Laravel app, but the screenshot you provided is actually flagging a
JavaScript/Node.js vulnerability
, not a PHP one.
The image shows an alert for...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32387
|
|
32388
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export
Copy
Show more options
Show the uploaded image in a lightbox
Copy prompt
Edit
You said I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
You said...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32388
|
|
32389
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export
Copy
Show more options
Show the uploaded image in a lightbox
Copy prompt
Edit
You said I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
You said
I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
Expand
Listen
Show thinking
Gemini said
Gemini said
It makes complete sense why you are confused! You were assigned a task to fix "Backend (BE) vulnerabilities" in your Laravel app, but the screenshot you provided is actually flagging a
JavaScript/Node.js vulnerability
, not a PHP one.
The image shows an alert for
npm-elliptic <= 6.6.1
, which is an
npm
(Node Package Manager) dependency. In modern Laravel applications,
npm
is typically used to manage frontend assets and build tools (like Vite or Laravel Mix), rather than backend PHP code (which uses Composer).
Here is exactly what you need to do to resolve this issue in your project:
1. Locate the Repository
1. Locate the Repository
The Vanta dashboard indicates this vulnerability is in a repository or project named
extension-app
. You need to open your terminal and navigate to the root directory of this specific project where the
package.json
file lives.
2. Identify How the Package is Used
2. Identify How the Package is Used
The package
elliptic
might be something your team installed directly, or (more likely) it is a "transitive dependency"—meaning another package you use relies on it.
Run this command in your terminal to see how it's being required:
Bash
Download code
Copy code
npm ls elliptic
This will output a tree showing exactly which package is bringing in the vulnerable version of
elliptic
.
3. Update the Vulnerable Package
3. Update the Vulnerable Package
You need to update
elliptic
to a version higher than
6.6.1
. You have a few options to do this:
Option A: The Automated Fix (Recommended First Step)
Run the built-in npm audit tool to automatically apply non-breaking updates:
Bash
Download code
Copy code
npm audit fix
Option B: Manual Update
If
elliptic
is a direct dependency in your
package.json
, run:
Bash
Download code
Copy code
npm update elliptic
Option C: Overriding a Transitive Dependency
If
npm audit fix
doesn't work because
elliptic
is deeply nested inside another package that hasn't updated its own dependencies, you can force a newer version by adding an
overrides
section to your
package.json
file:
JSON
Download code
Copy code
{
"dependencies"
: {
// your normal dependencies
},
"overrides"
: {
"elliptic"
:
"^6.6.2"
}
}
After adding that, run
npm install
to regenerate your
package-lock.json
.
4. Commit and Push
4. Commit and Push
Once you have updated the package, verify that your frontend assets still compile successfully (e.g., by running
npm run build
or
npm run dev
).
If everything works, commit the updated
package.json
and
package-lock.json
files and push them to your GitHub repository.
GitHub's Dependabot will automatically detect that the vulnerable version has been replaced and will mark the alert as resolved. Vanta will then sync with GitHub and clear the failing test from your dashboard!
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Panel
Panel
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Upg
Upg
Clear search
Clear search
More filters
App
App
Jira filter Space
Space
Jira filter Assignee
Assignee
Recent search Upg Recent search
Upg
Recent search
Recent search Upgrade Recent search
Upgrade
Recent search
RECENT
RECENT
Work item icon JY-2498: [PHP 8.2 Upgrade] Upgrade dependencies in composer.json to support PHP 8.x Jira • Technical Story • Jiminny (New) You viewed on 09 Mar 2026
JY-2498: [PHP 8.2
Upg
rade]
Upg
rade dependencies in composer.json to support PHP 8.x
Jira
•
Technical Story
•
Jiminny (New)
You viewed on
09 Mar 2026
Work item icon JY-19958: Upgrade BE libraries - May Jira • Technical Story • Jiminny (New) You viewed 1 day ago
JY-19958:
Upg
rade BE libraries - May
Jira
•
Technical Story
•...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32389
|
|
32393
|
[JY-6310] Upgrade Pipedrive API - Jira
[JY-6310] U [JY-6310] Upgrade Pipedrive API - Jira
[JY-6310] Upgrade Pipedrive API - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export
Copy
Show more options
Show the uploaded image in a lightbox
Copy prompt...
|
Firefox
|
[JY-6310] Upgrade Pipedrive API - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32393
|
|
32394
|
[JY-6310] Upgrade Pipedrive API - Jira
[JY-6310] U [JY-6310] Upgrade Pipedrive API - Jira
[JY-6310] Upgrade Pipedrive API - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export
Copy
Show more options
Show the uploaded image in a lightbox...
|
Firefox
|
[JY-6310] Upgrade Pipedrive API - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32394
|
|
32395
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export
Copy
Show more options
Show the uploaded image in a lightbox
Copy prompt
Edit
You said I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
You said
I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
Expand
Listen
Show thinking
Gemini said
Gemini said
It makes complete sense why you are confused! You were assigned a task to fix "Backend (BE) vulnerabilities" in your Laravel app, but the screenshot you provided is actually flagging a
JavaScript/Node.js vulnerability
, not a PHP one.
The image shows an alert for
npm-elliptic <= 6.6.1
, which is an
npm
(Node Package Manager) dependency. In modern Laravel applications,
npm
is typically used to manage frontend assets and build tools (like Vite or Laravel Mix), rather than backend PHP code (which uses Composer).
Here is exactly what you need to do to resolve this issue in your project:
1. Locate the Repository
1. Locate the Repository
The Vanta dashboard indicates this vulnerability is in a repository or project named
extension-app
. You need to open your terminal and navigate to the root directory of this specific project where the
package.json
file lives.
2. Identify How the Package is Used
2. Identify How the Package is Used
The package
elliptic
might be something your team installed directly, or (more likely) it is a "transitive dependency"—meaning another package you use relies on it.
Run this command in your terminal to see how it's being required:
Bash
Download code
Copy code
npm ls elliptic
This will output a tree showing exactly which package is bringing in the vulnerable version of
elliptic
.
3. Update the Vulnerable Package
3. Update the Vulnerable Package
You need to update
elliptic
to a version higher than
6.6.1
. You have a few options to do this:
Option A: The Automated Fix (Recommended First Step)
Run the built-in npm audit tool to automatically apply non-breaking updates:
Bash
Download code
Copy code
npm audit fix
Option B: Manual Update
If
elliptic
is a direct dependency in your
package.json
, run:
Bash
Download code
Copy code
npm update elliptic
Option C: Overriding a Transitive Dependency
If
npm audit fix
doesn't work because
elliptic
is deeply nested inside another package that hasn't updated its own dependencies, you can force a newer version by adding an
overrides
section to your
package.json
file:
JSON
Download code
Copy code
{
"dependencies"
: {
// your normal dependencies
},
"overrides"
: {
"elliptic"
:
"^6.6.2"
}
}
After adding that, run
npm install
to regenerate your
package-lock.json
.
4. Commit and Push
4. Commit and Push
Once you have updated the package, verify that your frontend assets still compile successfully (e.g., by running
npm run build
or
npm run dev
).
If everything works, commit the updated
package.json
and
package-lock.json
files and push them to your GitHub repository.
GitHub's Dependabot will automatically detect that the vulnerable version has been replaced and will mark the alert as resolved. Vanta will then sync with GitHub and clear the failing test from your dashboard!
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Panel
Panel
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Upg
Upg
Create
Create
Rovo Ask Rovo...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32395
|
|
32396
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export
Copy
Show more options
Show the uploaded image in a lightbox
Copy prompt
Edit
You said I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
You said
I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
Expand
Listen
Show thinking
Gemini said
Gemini said
It makes complete sense why you are confused! You were assigned a task to fix "Backend (BE) vulnerabilities" in your Laravel app, but the screenshot you provided is actually flagging a
JavaScript/Node.js vulnerability
, not a PHP one.
The image shows an alert for
npm-elliptic <= 6.6.1
, which is an
npm
(Node Package Manager) dependency. In modern Laravel applications,
npm
is typically used to manage frontend assets and build tools (like Vite or Laravel Mix), rather than backend PHP code (which uses Composer).
Here is exactly what you need to do to resolve this issue in your project:
1. Locate the Repository
1. Locate the Repository
The Vanta dashboard indicates this vulnerability is in a repository or project named
extension-app
. You need to open your terminal and navigate to the root directory of this specific project where the
package.json
file lives.
2. Identify How the Package is Used
2. Identify How the Package is Used
The package
elliptic
might be something your team installed directly, or (more likely) it is a "transitive dependency"—meaning another package you use relies on it.
Run this command in your terminal to see how it's being required:
Bash
Download code
Copy code
npm ls elliptic
This will output a tree showing exactly which package is bringing in the vulnerable version of
elliptic
.
3. Update the Vulnerable Package
3. Update the Vulnerable Package
You need to update
elliptic
to a version higher than
6.6.1
. You have a few options to do this:
Option A: The Automated Fix (Recommended First Step)
Run the built-in npm audit tool to automatically apply non-breaking updates:
Bash
Download code
Copy code
npm audit fix
Option B: Manual Update
If
elliptic
is a direct dependency in your
package.json
, run:
Bash
Download code
Copy code
npm update elliptic
Option C: Overriding a Transitive Dependency
If
npm audit fix
doesn't work because
elliptic
is deeply nested inside another package that hasn't updated its own dependencies, you can force a newer version by adding an
overrides
section to your
package.json
file:
JSON
Download code
Copy code
{
"dependencies"
: {
// your normal dependencies
},
"overrides"
: {
"elliptic"
:
"^6.6.2"
}
}
After adding that, run
npm install
to regenerate your
package-lock.json
.
4. Commit and Push
4. Commit and Push
Once you have updated the package, verify that your frontend assets still compile successfully (e.g., by running
npm run build
or
npm run dev
).
If everything works, commit the updated
package.json
and
package-lock.json
files and push them to your GitHub repository.
GitHub's Dependabot will automatically detect that the vulnerable version has been replaced and will mark the alert as resolved. Vanta will then sync with GitHub and clear the failing test from your dashboard!
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Panel
Panel
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Upg
Upg
Create...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32396
|
|
32397
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export
Copy
Show more options
Show the uploaded image in a lightbox
Copy prompt
Edit
You said I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
You said
I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
Expand
Listen
Show thinking
Gemini said
Gemini said
It makes complete sense why you are confused! You were assigned a task to fix "Backend (BE) vulnerabilities" in your Laravel app, but the screenshot you provided is actually flagging a
JavaScript/Node.js vulnerability
, not a PHP one.
The image shows an alert for
npm-elliptic <= 6.6.1
, which is an
npm
(Node Package Manager) dependency. In modern Laravel applications,
npm
is typically used to manage frontend assets and build tools (like Vite or Laravel Mix), rather than backend PHP code (which uses Composer).
Here is exactly what you need to do to resolve this issue in your project:
1. Locate the Repository
1. Locate the Repository
The Vanta dashboard indicates this vulnerability is in a repository or project named
extension-app
. You need to open your terminal and navigate to the root directory of this specific project where the
package.json
file lives.
2. Identify How the Package is Used
2. Identify How the Package is Used
The package
elliptic
might be something your team installed directly, or (more likely) it is a "transitive dependency"—meaning another package you use relies on it.
Run this command in your terminal to see how it's being required:
Bash
Download code
Copy code
npm ls elliptic
This will output a tree showing exactly which package is bringing in the vulnerable version of
elliptic
.
3. Update the Vulnerable Package
3. Update the Vulnerable Package
You need to update
elliptic
to a version higher than
6.6.1
. You have a few options to do this:
Option A: The Automated Fix (Recommended First Step)
Run the built-in npm audit tool to automatically apply non-breaking updates:
Bash
Download code
Copy code
npm audit fix
Option B: Manual Update
If
elliptic
is a direct dependency in your
package.json
, run:
Bash
Download code
Copy code
npm update elliptic
Option C: Overriding a Transitive Dependency
If
npm audit fix
doesn't work because
elliptic
is deeply nested inside another package that hasn't updated its own dependencies, you can force a newer version by adding an
overrides
section to your
package.json
file:
JSON
Download code
Copy code
{
"dependencies"
: {
// your normal dependencies
},
"overrides"
: {
"elliptic"
:
"^6.6.2"
}
}
After adding that, run
npm install
to regenerate your
package-lock.json
.
4. Commit and Push
4. Commit and Push
Once you have updated the package, verify that your frontend assets still compile successfully (e.g., by running
npm run build
or
npm run dev
).
If everything works, commit the updated
package.json
and
package-lock.json
files and push them to your GitHub repository.
GitHub's Dependabot will automatically detect that the vulnerable version has been replaced and will mark the alert as resolved. Vanta will then sync with GitHub and clear the failing test from your dashboard!
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Panel
Panel
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Upg
Upg
Create
Create
Rovo Ask Rovo
Ask Rovo
8 Notifications
8 Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
For you
For you
Recent
Recent
Starred
Starred
Apps
Apps
More actions for Apps
More actions for Apps
Spaces
Spaces
Create space
Create space
More actions for spaces
More actions for spaces
Recent
Jiminny (New)
Jiminny (New)
Jiminny (New)
Create board
Create board
More actions for Jiminny (New)
More actions for Jiminny (New)
Platform Team
Platform Team
Board actions
Board actions
Capture Team
Capture Team
Board actions
Board actions
Enterprise Stability Issues 🤕
Enterprise Stability Issues 🤕
Board actions
Board actions
Processing Team...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32397
|
|
32398
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export
Copy
Show more options
Show the uploaded image in a lightbox
Copy prompt
Edit
You said I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
You said
I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
Expand
Listen
Show thinking
Gemini said
Gemini said
It makes complete sense why you are confused! You were assigned a task to fix "Backend (BE) vulnerabilities" in your Laravel app, but the screenshot you provided is actually flagging a
JavaScript/Node.js vulnerability
, not a PHP one.
The image shows an alert for
npm-elliptic <= 6.6.1
, which is an
npm
(Node Package Manager) dependency. In modern Laravel applications,
npm
is typically used to manage frontend assets and build tools (like Vite or Laravel Mix), rather than backend PHP code (which uses Composer).
Here is exactly what you need to do to resolve this issue in your project:
1. Locate the Repository
1. Locate the Repository
The Vanta dashboard indicates this vulnerability is in a repository or project named
extension-app
. You need to open your terminal and navigate to the root directory of this specific project where the
package.json
file lives.
2. Identify How the Package is Used
2. Identify How the Package is Used
The package
elliptic
might be something your team installed directly, or (more likely) it is a "transitive dependency"—meaning another package you use relies on it.
Run this command in your terminal to see how it's being required:
Bash
Download code
Copy code
npm ls elliptic
This will output a tree showing exactly which package is bringing in the vulnerable version of
elliptic
.
3. Update the Vulnerable Package
3. Update the Vulnerable Package
You need to update
elliptic
to a version higher than
6.6.1
. You have a few options to do this:
Option A: The Automated Fix (Recommended First Step)
Run the built-in npm audit tool to automatically apply non-breaking updates:
Bash
Download code
Copy code
npm audit fix
Option B: Manual Update
If
elliptic
is a direct dependency in your
package.json
, run:
Bash
Download code
Copy code
npm update elliptic
Option C: Overriding a Transitive Dependency
If
npm audit fix
doesn't work because
elliptic
is deeply nested inside another package that hasn't updated its own dependencies, you can force a newer version by adding an
overrides
section to your
package.json
file:
JSON
Download code
Copy code
{
"dependencies"
: {
// your normal dependencies
},
"overrides"
: {
"elliptic"
:
"^6.6.2"
}
}
After adding that, run
npm install
to regenerate your
package-lock.json
.
4. Commit and Push
4. Commit and Push
Once you have updated the package, verify that your frontend assets still compile successfully (e.g., by running
npm run build
or
npm run dev
).
If everything works, commit the updated
package.json
and
package-lock.json
files and push them to your GitHub repository.
GitHub's Dependabot will automatically detect that the vulnerable version has been replaced and will mark the alert as resolved. Vanta will then sync with GitHub and clear the failing test from your dashboard!
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Panel
Panel
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Upg
Upg
Clear search
Clear search
More filters
App
App
Jira filter Space
Space
Jira filter Assignee
Assignee
Recent search Upg Recent search
Upg
Recent search
Recent search Upgrade Recent search
Upgrade
Recent search
RECENT
RECENT
Work item icon JY-2498: [PHP 8.2 Upgrade] Upgrade dependencies in composer.json to support PHP 8.x Jira • Technical Story • Jiminny (New) You viewed on 09 Mar 2026
JY-2498: [PHP 8.2
Upg
rade]
Upg
rade dependencies in composer.json to support PHP 8.x
Jira
•
Technical Story
•
Jiminny (New)
You viewed on
09 Mar 2026...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32398
|
|
32399
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export
Copy
Show more options
Show the uploaded image in a lightbox
Copy prompt
Edit
You said I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
You said
I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
Expand
Listen
Show thinking
Gemini said
Gemini said
It makes complete sense why you are confused! You were assigned a task to fix "Backend (BE) vulnerabilities" in your Laravel app, but the screenshot you provided is actually flagging a
JavaScript/Node.js vulnerability
, not a PHP one.
The image shows an alert for
npm-elliptic <= 6.6.1
, which is an
npm
(Node Package Manager) dependency. In modern Laravel applications,
npm
is typically used to manage frontend assets and build tools (like Vite or Laravel Mix), rather than backend PHP code (which uses Composer).
Here is exactly what you need to do to resolve this issue in your project:
1. Locate the Repository
1. Locate the Repository
The Vanta dashboard indicates this vulnerability is in a repository or project named
extension-app
. You need to open your terminal and navigate to the root directory of this specific project where the
package.json
file lives.
2. Identify How the Package is Used
2. Identify How the Package is Used
The package
elliptic
might be something your team installed directly, or (more likely) it is a "transitive dependency"—meaning another package you use relies on it.
Run this command in your terminal to see how it's being required:
Bash
Download code
Copy code
npm ls elliptic
This will output a tree showing exactly which package is bringing in the vulnerable version of
elliptic
.
3. Update the Vulnerable Package
3. Update the Vulnerable Package
You need to update
elliptic
to a version higher than
6.6.1
. You have a few options to do this:
Option A: The Automated Fix (Recommended First Step)
Run the built-in npm audit tool to automatically apply non-breaking updates:
Bash
Download code
Copy code
npm audit fix
Option B: Manual Update
If
elliptic
is a direct dependency in your
package.json
, run:
Bash
Download code
Copy code
npm update elliptic
Option C: Overriding a Transitive Dependency
If
npm audit fix
doesn't work because
elliptic
is deeply nested inside another package that hasn't updated its own dependencies, you can force a newer version by adding an
overrides
section to your
package.json
file:
JSON
Download code
Copy code
{
"dependencies"
: {
// your normal dependencies
},
"overrides"
: {
"elliptic"
:
"^6.6.2"
}
}
After adding that, run
npm install
to regenerate your
package-lock.json
.
4. Commit and Push
4. Commit and Push
Once you have updated the package, verify that your frontend assets still compile successfully (e.g., by running
npm run build
or
npm run dev
).
If everything works, commit the updated
package.json
and
package-lock.json
files and push them to your GitHub repository.
GitHub's Dependabot will automatically detect that the vulnerable version has been replaced and will mark the alert as resolved. Vanta will then sync with GitHub and clear the failing test from your dashboard!
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Panel
Panel
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Upg
Upg
Clear search
Clear search
More filters
App
App
Jira filter Space
Space
Jira filter Assignee
Assignee
Recent search Upg Recent search
Upg
Recent search
Recent search Upgrade Recent search
Upgrade
Recent search
RECENT
RECENT
Work item icon JY-2498: [PHP 8.2 Upgrade] Upgrade dependencies in composer.json to support PHP 8.x Jira • Technical Story • Jiminny (New) You viewed on 09 Mar 2026
JY-2498: [PHP 8.2
Upg
rade]
Upg
rade dependencies in composer.json to support PHP 8.x
Jira
•
Technical Story
•
Jiminny (New)
You viewed on
09 Mar 2026
Work item icon JY-19958: Upgrade BE libraries - May Jira • Technical Story • Jiminny (New) You viewed 1 day ago
JY-19958:
Upg
rade BE libraries - May
Jira
•
Technical Story
•
Jiminny (New)
You viewed
1 day ago
Work item icon JY-6310: Upgrade Pipedrive API Jira • Epic • Jiminny (New) You viewed 5 days ago
JY-6310:
Upg
rade Pipedrive API
Jira
•
Epic...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32399
|
|
32400
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export
Copy
Show more options
Show the uploaded image in a lightbox
Copy prompt
Edit
You said I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
You said
I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
Expand
Listen
Show thinking
Gemini said
Gemini said
It makes complete sense why you are confused! You were assigned a task to fix "Backend (BE) vulnerabilities" in your Laravel app, but the screenshot you provided is actually flagging a
JavaScript/Node.js vulnerability
, not a PHP one.
The image shows an alert for
npm-elliptic <= 6.6.1
, which is an
npm
(Node Package Manager) dependency. In modern Laravel applications,
npm
is typically used to manage frontend assets and build tools (like Vite or Laravel Mix), rather than backend PHP code (which uses Composer).
Here is exactly what you need to do to resolve this issue in your project:
1. Locate the Repository
1. Locate the Repository
The Vanta dashboard indicates this vulnerability is in a repository or project named
extension-app
. You need to open your terminal and navigate to the root directory of this specific project where the
package.json
file lives.
2. Identify How the Package is Used
2. Identify How the Package is Used
The package
elliptic
might be something your team installed directly, or (more likely) it is a "transitive dependency"—meaning another package you use relies on it.
Run this command in your terminal to see how it's being required:
Bash
Download code
Copy code
npm ls elliptic
This will output a tree showing exactly which package is bringing in the vulnerable version of
elliptic
.
3. Update the Vulnerable Package
3. Update the Vulnerable Package
You need to update
elliptic
to a version higher than
6.6.1
. You have a few options to do this:
Option A: The Automated Fix (Recommended First Step)
Run the built-in npm audit tool to automatically apply non-breaking updates:
Bash
Download code
Copy code
npm audit fix
Option B: Manual Update
If
elliptic
is a direct dependency in your
package.json
, run:
Bash
Download code
Copy code
npm update elliptic
Option C: Overriding a Transitive Dependency
If
npm audit fix
doesn't work because
elliptic
is deeply nested inside another package that hasn't updated its own dependencies, you can force a newer version by adding an
overrides
section to your
package.json
file:
JSON
Download code
Copy code
{
"dependencies"
: {
// your normal dependencies
},
"overrides"
: {
"elliptic"
:
"^6.6.2"
}
}
After adding that, run
npm install
to regenerate your
package-lock.json
.
4. Commit and Push
4. Commit and Push
Once you have updated the package, verify that your frontend assets still compile successfully (e.g., by running
npm run build
or
npm run dev
).
If everything works, commit the updated
package.json
and
package-lock.json
files and push them to your GitHub repository.
GitHub's Dependabot will automatically detect that the vulnerable version has been replaced and will mark the alert as resolved. Vanta will then sync with GitHub and clear the failing test from your dashboard!
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Panel
Panel
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Figma is now available!
Connect your account to see missing results
Connect
Dismiss
Dismiss
More filters
App
App
Jira filter Space
Space
Jira filter Assignee
Assignee
Suggestion search Recent open items assigned to Nikolay Yankov Suggestion
Recent open items assigned to Nikolay Yankov
Suggestion
Suggestion search Recent tickets created by me Suggestion
Recent tickets created by me
Suggestion
Recent search Upg Recent search
Upg
Recent search
RECENT
RECENT
Work item icon JY-20773: User Pilot not receiving events on report generated Jira • Bug • Jiminny (New) You worked on 19 hours ago
JY-20773: User Pilot not receiving events on report generated
Jira
•
Bug
•
Jiminny (New)
You worked on
19 hours ago
Work item icon JY-20776: Automated report - sentry Jira • Bug • Jiminny (New) You viewed 19 hours ago
JY-20776: Automated report - sentry
Jira
•
Bug
•
Jiminny (New)
You viewed
19 hours ago
Work item icon JY-19958: Upgrade BE libraries - May Jira • Technical Story • Jiminny (New) You viewed 1 day ago
JY-19958: Upgrade BE libraries - May
Jira
•
Technical Story
•
Jiminny (New)
You viewed
1 day ago
Work item icon SRD-6793: Les Mills activity types not pulling in Jira • Bug • Service-Desk You viewed 1 day ago
SRD-6793: Les Mills activity types not pulling in
Jira
•
Bug
•
Service-Desk
You viewed
1 day ago
Work item icon JY-20625: [POC]Jiminny MCP Connector Jira • Spike • Jiminny (New) You viewed 1 day ago
JY-20625: [POC]Jiminny MCP Connector
Jira
•
Spike
•
Jiminny (New)
You viewed
1 day ago
Work item icon JY-20361: AJ Panorama for Call Scoring in OD Jira • Story • Jiminny (New) You viewed 1 day ago
JY-20361: AJ Panorama for Call Scoring in OD
Jira
•
Story
•
Jiminny (New)
You viewed
1 day ago
Work item icon JY-20725: [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts Jira • Bug • Jiminny (New) You viewed 1 day ago
JY-20725: [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts
Jira
•
Bug
•
Jiminny (New)
You viewed
1 day ago
Boards
Boards
Spaces
Spaces
Filters
Filters
Plans
Plans
Teams
Teams
Search Jira for work items
Search Jira for work items
Search all apps +2
Search all apps
+2
Help us improve search
Give feedback
Why has search changed? Link to community post , (opens new window)
Why has search changed?
, (opens new window)
12 options available
Create
Create
Rovo Ask Rovo
Ask Rovo
8 Notifications
8 Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
For you
For you...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32400
|
|
32401
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export
Copy
Show more options
Show the uploaded image in a lightbox
Copy prompt
Edit
You said I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
You said
I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
Expand
Listen
Show thinking
Gemini said
Gemini said
It makes complete sense why you are confused! You were assigned a task to fix "Backend (BE) vulnerabilities" in your Laravel app, but the screenshot you provided is actually flagging a
JavaScript/Node.js vulnerability
, not a PHP one.
The image shows an alert for
npm-elliptic <= 6.6.1
, which is an
npm
(Node Package Manager) dependency. In modern Laravel applications,
npm
is typically used to manage frontend assets and build tools (like Vite or Laravel Mix), rather than backend PHP code (which uses Composer).
Here is exactly what you need to do to resolve this issue in your project:
1. Locate the Repository
1. Locate the Repository
The Vanta dashboard indicates this vulnerability is in a repository or project named
extension-app
. You need to open your terminal and navigate to the root directory of this specific project where the
package.json
file lives.
2. Identify How the Package is Used
2. Identify How the Package is Used
The package
elliptic
might be something your team installed directly, or (more likely) it is a "transitive dependency"—meaning another package you use relies on it.
Run this command in your terminal to see how it's being required:
Bash
Download code
Copy code
npm ls elliptic
This will output a tree showing exactly which package is bringing in the vulnerable version of
elliptic
.
3. Update the Vulnerable Package
3. Update the Vulnerable Package
You need to update
elliptic
to a version higher than
6.6.1
. You have a few options to do this:
Option A: The Automated Fix (Recommended First Step)
Run the built-in npm audit tool to automatically apply non-breaking updates:
Bash
Download code
Copy code
npm audit fix
Option B: Manual Update
If
elliptic
is a direct dependency in your
package.json
, run:
Bash
Download code
Copy code
npm update elliptic
Option C: Overriding a Transitive Dependency
If
npm audit fix
doesn't work because
elliptic
is deeply nested inside another package that hasn't updated its own dependencies, you can force a newer version by adding an
overrides
section to your
package.json
file:
JSON
Download code
Copy code
{
"dependencies"
: {
// your normal dependencies
},
"overrides"
: {
"elliptic"
:
"^6.6.2"
}
}
After adding that, run
npm install
to regenerate your
package-lock.json
.
4. Commit and Push
4. Commit and Push
Once you have updated the package, verify that your frontend assets still compile successfully (e.g., by running
npm run build
or
npm run dev
).
If everything works, commit the updated
package.json
and
package-lock.json
files and push them to your GitHub repository.
GitHub's Dependabot will automatically detect that the vulnerable version has been replaced and will mark the alert as resolved. Vanta will then sync with GitHub and clear the failing test from your dashboard!
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32401
|
|
32402
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export
Copy
Show more options
Show the uploaded image in a lightbox
Copy prompt
Edit
You said I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
You said
I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
Expand
Listen
Show thinking
Gemini said
Gemini said
It makes complete sense why you are confused! You were assigned a task to fix "Backend (BE) vulnerabilities" in your Laravel app, but the screenshot you provided is actually flagging a
JavaScript/Node.js vulnerability
, not a PHP one.
The image shows an alert for
npm-elliptic <= 6.6.1
, which is an
npm
(Node Package Manager) dependency. In modern Laravel applications,
npm
is typically used to manage frontend assets and build tools (like Vite or Laravel Mix), rather than backend PHP code (which uses Composer).
Here is exactly what you need to do to resolve this issue in your project:
1. Locate the Repository
1. Locate the Repository
The Vanta dashboard indicates this vulnerability is in a repository or project named
extension-app
. You need to open your terminal and navigate to the root directory of this specific project where the
package.json
file lives.
2. Identify How the Package is Used
2. Identify How the Package is Used
The package
elliptic
might be something your team installed directly, or (more likely) it is a "transitive dependency"—meaning another package you use relies on it.
Run this command in your terminal to see how it's being required:
Bash
Download code
Copy code
npm ls elliptic
This will output a tree showing exactly which package is bringing in the vulnerable version of
elliptic
.
3. Update the Vulnerable Package
3. Update the Vulnerable Package
You need to update
elliptic
to a version higher than
6.6.1
. You have a few options to do this:
Option A: The Automated Fix (Recommended First Step)
Run the built-in npm audit tool to automatically apply non-breaking updates:
Bash
Download code
Copy code
npm audit fix
Option B: Manual Update
If
elliptic
is a direct dependency in your
package.json
, run:
Bash
Download code
Copy code
npm update elliptic
Option C: Overriding a Transitive Dependency
If
npm audit fix
doesn't work because
elliptic
is deeply nested inside another package that hasn't updated its own dependencies, you can force a newer version by adding an
overrides
section to your
package.json
file:
JSON
Download code
Copy code
{
"dependencies"
: {
// your normal dependencies
},
"overrides"
: {
"elliptic"
:
"^6.6.2"
}
}
After adding that, run
npm install
to regenerate your
package-lock.json
.
4. Commit and Push
4. Commit and Push
Once you have updated the package, verify that your frontend assets still compile successfully (e.g., by running
npm run build
or
npm run dev
).
If everything works, commit the updated
package.json
and
package-lock.json
files and push them to your GitHub repository.
GitHub's Dependabot will automatically detect that the vulnerable version has been replaced and will mark the alert as resolved. Vanta will then sync with GitHub and clear the failing test from your dashboard!
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Panel
Panel
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
BE
BE
Clear search
Clear search
More filters
App
App
Jira filter Space
Space
Jira filter Assignee
Assignee
RECENT
RECENT
Work item icon JY-20679: [BE] Add dash symbol between name and period in the title Jira • Sub-task • Jiminny (New) You worked on 17 Apr 2026
JY-20679: [
BE
] Add dash symbol
be
tween name and period in the title
Jira
•
Sub-task
•
Jiminny (New)
You worked on
17 Apr 2026
Work item icon JY-19958: Upgrade BE libraries - May Jira • Technical Story • Jiminny (New) You viewed 1 day ago
JY-19958: Upgrade
BE
libraries - May
Jira
•
Technical Story
•
Jiminny (New)
You viewed
1 day ago
Work item icon JY-19957: Upgrade BE libraries - Apr Jira • Technical Story • Jiminny (New) You viewed on 15 Apr 2026
JY-19957: Upgrade
BE
libraries - Apr
Jira
•
Technical Story
•
Jiminny (New)
You viewed on
15 Apr 2026
Work item icon JY-20573: [BE] Manage recipients for email sending Jira • Sub-task • Jiminny (New) You worked on 12 Apr 2026
JY-20573: [
BE
] Manage recipients for email sending
Jira
•
Sub-task
•
Jiminny (New)
You worked on
12 Apr 2026
Work item icon JY-20572: [BE] Send email for generated report (check design) Jira • Sub-task • Jiminny (New) You worked on 12 Apr 2026
JY-20572: [
BE
] Send email for generated report (check design)
Jira
•
Sub-task
•
Jiminny (New)
You worked on
12 Apr 2026
SEARCH RESULTS
SEARCH RESULTS
Work item icon JY-20361: AJ Panorama for Call Scoring in OD Jira • Story • Jiminny (New) Updated 2 hours ago
JY-20361: AJ Panorama for Call Scoring in OD
Jira
•
Story
•
Jiminny (New)
Updated
2 hours ago
Work item icon JY-19628: Evaluation of AJ Panorama Jira • Technical Story • Jiminny (New) Updated 2 hours ago
JY-19628: Evaluation of AJ Panorama
Jira
•
Technical Story
•
Jiminny (New)
Updated
2 hours ago
Work item icon JY-20412: Change Auto-log delay Jira • Story • Jiminny (New) Updated 3 hours ago
JY-20412: Change Auto-log delay
Jira
•
Story
•
Jiminny (New)
Updated
3 hours ago...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32402
|
|
32403
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32403
|
|
32404
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32404
|
|
32405
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export
Copy
Show more options
Show the uploaded image in a lightbox
Copy prompt
Edit
You said I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
You said
I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
Expand
Listen
Show thinking
Gemini said
Gemini said
It makes complete sense why you are confused! You were assigned a task to fix "Backend (BE) vulnerabilities" in your Laravel app, but the screenshot you provided is actually flagging a
JavaScript/Node.js vulnerability
, not a PHP one.
The image shows an alert for
npm-elliptic <= 6.6.1
, which is an
npm
(Node Package Manager) dependency. In modern Laravel applications,
npm
is typically used to manage frontend assets and build tools (like Vite or Laravel Mix), rather than backend PHP code (which uses Composer).
Here is exactly what you need to do to resolve this issue in your project:
1. Locate the Repository
1. Locate the Repository
The Vanta dashboard indicates this vulnerability is in a repository or project named
extension-app
. You need to open your terminal and navigate to the root directory of this specific project where the
package.json
file lives.
2. Identify How the Package is Used
2. Identify How the Package is Used
The package
elliptic
might be something your team installed directly, or (more likely) it is a "transitive dependency"—meaning another package you use relies on it....
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32405
|
|
32406
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export
Copy
Show more options
Show the uploaded image in a lightbox
Copy prompt
Edit
You said I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
You said
I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
Expand
Listen
Show thinking
Gemini said
Gemini said
It makes complete sense why you are confused! You were assigned a task to fix "Backend (BE) vulnerabilities" in your Laravel app, but the screenshot you provided is actually flagging a
JavaScript/Node.js vulnerability
, not a PHP one.
The image shows an alert for
npm-elliptic <= 6.6.1
, which is an
npm
(Node Package Manager) dependency. In modern Laravel applications,
npm
is typically used to manage frontend assets and build tools (like Vite or Laravel Mix), rather than backend PHP code (which uses Composer).
Here is exactly what you need to do to resolve this issue in your project:
1. Locate the Repository
1. Locate the Repository
The Vanta dashboard indicates this vulnerability is in a repository or project named
extension-app
. You need to open your terminal and navigate to the root directory of this specific project where the
package.json
file lives.
2. Identify How the Package is Used
2. Identify How the Package is Used
The package
elliptic
might be something your team installed directly, or (more likely) it is a "transitive dependency"—meaning another package you use relies on it.
Run this command in your terminal to see how it's being required:
Bash
Download code...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32406
|
|
32407
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export
Copy
Show more options
Show the uploaded image in a lightbox
Copy prompt
Edit
You said I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
You said
I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
Expand
Listen
Show thinking
Gemini said
Gemini said
It makes complete sense why you are confused! You were assigned a task to fix "Backend (BE) vulnerabilities" in your Laravel app, but the screenshot you provided is actually flagging a
JavaScript/Node.js vulnerability
, not a PHP one.
The image shows an alert for
npm-elliptic <= 6.6.1
, which is an
npm
(Node Package Manager) dependency. In modern Laravel applications,
npm
is typically used to manage frontend assets and build tools (like Vite or Laravel Mix), rather than backend PHP code (which uses Composer).
Here is exactly what you need to do to resolve this issue in your project:
1. Locate the Repository
1. Locate the Repository
The Vanta dashboard indicates this vulnerability is in a repository or project named
extension-app
. You need to open your terminal and navigate to the root directory of this specific project where the
package.json
file lives.
2. Identify How the Package is Used
2. Identify How the Package is Used
The package
elliptic
might be something your team installed directly, or (more likely) it is a "transitive dependency"—meaning another package you use relies on it.
Run this command in your terminal to see how it's being required:
Bash
Download code
Copy code
npm ls elliptic
This will output a tree showing exactly which package is bringing in the vulnerable version of
elliptic
.
3. Update the Vulnerable Package
3. Update the Vulnerable Package
You need to update
elliptic
to a version higher than
6.6.1
. You have a few options to do this:
Option A: The Automated Fix (Recommended First Step)
Run the built-in npm audit tool to automatically apply non-breaking updates:
Bash
Download code
Copy code
npm audit fix
Option B: Manual Update
If
elliptic
is a direct dependency in your
package.json
, run:
Bash
Download code
Copy code
npm update elliptic
Option C: Overriding a Transitive Dependency
If
npm audit fix
doesn't work because
elliptic
is deeply nested inside another package that hasn't updated its own dependencies, you can force a newer version by adding an
overrides
section to your
package.json
file:
JSON
Download code
Copy code
{
"dependencies"
: {
// your normal dependencies
},
"overrides"
: {
"elliptic"
:
"^6.6.2"
}
}
After adding that, run
npm install
to regenerate your
package-lock.json
.
4. Commit and Push
4. Commit and Push
Once you have updated the package, verify that your frontend assets still compile successfully (e.g., by running
npm run build
or
npm run dev
).
If everything works, commit the updated
package.json
and
package-lock.json
files and push them to your GitHub repository.
GitHub's Dependabot will automatically detect that the vulnerable version has been replaced and will mark the alert as resolved. Vanta will then sync with GitHub and clear the failing test from your dashboard!
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Panel
Panel
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
8 Notifications
8 Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
For you
For you
Recent
Recent
Starred
Starred
Apps
Apps
More actions for Apps
More actions for Apps
Spaces
Spaces
Create space
Create space
More actions for spaces
More actions for spaces
Recent
Jiminny (New)...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32407
|
|
32415
|
Platform Team - Timeline - Jira
Platform Team - Ti Platform Team - Timeline - Jira
Platform Team - Timeline - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export
Copy
Show more options
Show the uploaded image in a lightbox
Copy prompt
Edit
You said I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
You said
I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
Expand
Listen
Show thinking
Gemini said
Gemini said
It makes complete sense why you are confused! You were assigned a task to fix "Backend (BE) vulnerabilities" in your Laravel app, but the screenshot you provided is actually flagging a
JavaScript/Node.js vulnerability
, not a PHP one.
The image shows an alert for
npm-elliptic <= 6.6.1
, which is an
npm
(Node Package Manager) dependency. In modern Laravel applications,
npm
is typically used to manage frontend assets and build tools (like Vite or Laravel Mix), rather than backend PHP code (which uses Composer).
Here is exactly what you need to do to resolve this issue in your project:
1. Locate the Repository
1. Locate the Repository
The Vanta dashboard indicates this vulnerability is in a repository or project named
extension-app
. You need to open your terminal and navigate to the root directory of this specific project where the
package.json
file lives.
2. Identify How the Package is Used
2. Identify How the Package is Used
The package
elliptic
might be something your team installed directly, or (more likely) it is a "transitive dependency"—meaning another package you use relies on it.
Run this command in your terminal to see how it's being required:
Bash
Download code
Copy code
npm ls elliptic
This will output a tree showing exactly which package is bringing in the vulnerable version of
elliptic
.
3. Update the Vulnerable Package
3. Update the Vulnerable Package
You need to update
elliptic
to a version higher than
6.6.1
. You have a few options to do this:
Option A: The Automated Fix (Recommended First Step)
Run the built-in npm audit tool to automatically apply non-breaking updates:
Bash
Download code
Copy code
npm audit fix
Option B: Manual Update
If
elliptic
is a direct dependency in your
package.json
, run:
Bash
Download code
Copy code
npm update elliptic
Option C: Overriding a Transitive Dependency
If
npm audit fix
doesn't work because
elliptic
is deeply nested inside another package that hasn't updated its own dependencies, you can force a newer version by adding an
overrides
section to your
package.json
file:
JSON
Download code
Copy code
{
"dependencies"
: {
// your normal dependencies
},
"overrides"
: {
"elliptic"
:
"^6.6.2"
}
}
After adding that, run
npm install
to regenerate your
package-lock.json
.
4. Commit and Push
4. Commit and Push
Once you have updated the package, verify that your frontend assets still compile successfully (e.g., by running
npm run build
or
npm run dev
).
If everything works, commit the updated
package.json
and
package-lock.json
files and push them to your GitHub repository.
GitHub's Dependabot will automatically detect that the vulnerable version has been replaced and will mark the alert as resolved. Vanta will then sync with GitHub and clear the failing test from your dashboard!
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu...
|
Firefox
|
Platform Team - Timeline - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32415
|
|
32416
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export
Copy
Show more options
Show the uploaded image in a lightbox
Copy prompt
Edit
You said I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
You said
I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
Expand
Listen
Show thinking
Gemini said
Gemini said
It makes complete sense why you are confused! You were assigned a task to fix "Backend (BE) vulnerabilities" in your Laravel app, but the screenshot you provided is actually flagging a
JavaScript/Node.js vulnerability
, not a PHP one.
The image shows an alert for
npm-elliptic <= 6.6.1
, which is an
npm
(Node Package Manager) dependency. In modern Laravel applications,
npm
is typically used to manage frontend assets and build tools (like Vite or Laravel Mix), rather than backend PHP code (which uses Composer).
Here is exactly what you need to do to resolve this issue in your project:
1. Locate the Repository
1. Locate the Repository
The Vanta dashboard indicates this vulnerability is in a repository or project named
extension-app
. You need to open your terminal and navigate to the root directory of this specific project where the
package.json
file lives.
2. Identify How the Package is Used
2. Identify How the Package is Used
The package
elliptic
might be something your team installed directly, or (more likely) it is a "transitive dependency"—meaning another package you use relies on it.
Run this command in your terminal to see how it's being required:
Bash
Download code
Copy code
npm ls elliptic
This will output a tree showing exactly which package is bringing in the vulnerable version of
elliptic
.
3. Update the Vulnerable Package
3. Update the Vulnerable Package
You need to update
elliptic
to a version higher than
6.6.1
. You have a few options to do this:
Option A: The Automated Fix (Recommended First Step)
Run the built-in npm audit tool to automatically apply non-breaking updates:
Bash
Download code
Copy code
npm audit fix
Option B: Manual Update
If
elliptic
is a direct dependency in your
package.json
, run:
Bash
Download code
Copy code
npm update elliptic
Option C: Overriding a Transitive Dependency
If
npm audit fix
doesn't work because
elliptic
is deeply nested inside another package that hasn't updated its own dependencies, you can force a newer version by adding an
overrides
section to your
package.json
file:
JSON
Download code
Copy code
{
"dependencies"
: {
// your normal dependencies
},
"overrides"
: {
"elliptic"
:
"^6.6.2"
}
}
After adding that, run
npm install
to regenerate your
package-lock.json
.
4. Commit and Push
4. Commit and Push
Once you have updated the package, verify that your frontend assets still compile successfully (e.g., by running
npm run build
or
npm run dev
).
If everything works, commit the updated
package.json
and
package-lock.json
files and push them to your GitHub repository.
GitHub's Dependabot will automatically detect that the vulnerable version has been replaced and will mark the alert as resolved. Vanta will then sync with GitHub and clear the failing test from your dashboard!
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32416
|
|
32417
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export
Copy
Show more options
Show the uploaded image in a lightbox
Copy prompt
Edit
You said I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
You said
I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
Expand
Listen
Show thinking
Gemini said
Gemini said
It makes complete sense why you are confused! You were assigned a task to fix "Backend (BE) vulnerabilities" in your Laravel app, but the screenshot you provided is actually flagging a
JavaScript/Node.js vulnerability
, not a PHP one.
The image shows an alert for
npm-elliptic <= 6.6.1
, which is an
npm
(Node Package Manager) dependency. In modern Laravel applications,
npm
is typically used to manage frontend assets and build tools (like Vite or Laravel Mix), rather than backend PHP code (which uses Composer).
Here is exactly what you need to do to resolve this issue in your project:
1. Locate the Repository
1. Locate the Repository
The Vanta dashboard indicates this vulnerability is in a repository or project named
extension-app
. You need to open your terminal and navigate to the root directory of this specific project where the
package.json
file lives.
2. Identify How the Package is Used
2. Identify How the Package is Used
The package
elliptic
might be something your team installed directly, or (more likely) it is a "transitive dependency"—meaning another package you use relies on it.
Run this command in your terminal to see how it's being required:
Bash
Download code
Copy code
npm ls elliptic
This will output a tree showing exactly which package is bringing in the vulnerable version of
elliptic
.
3. Update the Vulnerable Package
3. Update the Vulnerable Package...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32417
|
|
32418
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Close tab
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
jiminny/app/backend-code - Vanta
jiminny/app/backend-code - Vanta
NVD - cve-2026-6722
NVD - cve-2026-6722
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
Project Phoenix – Figma
Project Phoenix – Figma
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
New Tab
New Tab
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
[JY-19957] Upgrade BE libraries - Apr - Jira
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
JY-19957 | Remove abanded sympfony debug, compose upgrade by nikolaybiaivanov · Pull Request #12022 · jiminny/app
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
High vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Medium vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
Low vulnerabilities identified in packages are addressed (GitHub Repo) - Vanta
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution. Metrics NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed. CVSS 3.x Severity and Vector Strings: NIST: NVD Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H References to Advisories, Solutions, and Tools By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [EMAIL]. URL Source(s) Tag(s) https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5 PHP Group Vendor Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-416 Use After Free PHP Group Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s) From (including)8.5.0Up to (excluding)8.5.6 Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 2 change records found show changes</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>NVD - cve-2026-6722</tabTitle>” with “<selection>Description
In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
CVSS 3.x Severity and Vector Strings:
NIST: NVD
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [EMAIL].
URL
Source(s)
Tag(s)
https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
PHP Group
Vendor Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-416
Use After Free
PHP Group
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.2.0Up to (excluding)8.2.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.3.0Up to (excluding)8.3.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.4.0Up to (excluding)8.4.21 cpe:2.3:a:php:php:*:*:*:*:*:*:*:* Show Matching CPE(s)
From (including)8.5.0Up to (excluding)8.5.6
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
2 change records found show changes</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Gemini said
Gemini said
Summary of CVE-2026-6722
Summary of CVE-2026-6722
Vulnerability Overview
A Use-After-Free (UAF) vulnerability exists in the PHP SOAP extension due to a flaw in its object deduplication mechanism. The system stores pointers to PHP objects in a global map without properly incrementing their reference counts, leading to memory corruption.
Technical Mechanism
Root Cause:
When processing an
apache:Map
node with duplicate keys, the second entry overwrites the first in a temporary result map.
Memory Corruption:
This overwrite frees the original PHP object, but a "stale" (dangling) pointer remains in the global map.
Exploitation:
An attacker can use an
href
reference to the freed node to copy the dangling pointer. By manipulating SOAP request bodies, an attacker can reclaim that memory region with PHP string allocations.
Impact:
Successful exploitation allows for
Remote Code Execution (RCE)
.
Risk Assessment
CVSS 3.1 Score:
9.8 (Critical)
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Type:
CWE-416 (Use After Free)
Affected Software
The following PHP versions are vulnerable:
8.2.x:
Versions 8.2.0 up to (but excluding) 8.2.31
8.3.x:
Versions 8.3.0 up to (but excluding) 8.3.31
8.4.x:
Versions 8.4.0 up to (but excluding) 8.4.21
8.5.x:
Versions 8.5.0 up to (but excluding) 8.5.6
Solution
Users should update to the patched versions (8.2.31, 8.3.31, 8.4.21, or 8.5.6) as identified in the vendor advisory.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
You said how can I do it? I am in laravel app.
You said
how can I do it? I am in laravel app.
Listen
Show thinking
Gemini said
Gemini said
I cannot provide exploit instructions or payloads for CVE-2026-6722. I can, however, show you how to check if your Laravel application's environment is vulnerable and how to secure it against this threat.
Because this is a vulnerability in PHP's core C code (specifically the SOAP extension) rather than in Laravel's PHP code, fixing it requires evaluating your server environment.
Here is how you can assess your risk and secure your application.
1. Check if the SOAP Extension is Enabled
1. Check if the SOAP Extension is Enabled
Laravel does not use or require the PHP SOAP extension by default. Your application is only at risk if the extension is enabled and your application is parsing untrusted SOAP requests (e.g., through a specific package or custom integration).
To check via the Command Line (CLI):
Run the following command in your terminal. If it outputs
soap
, the extension is enabled for your CLI.
Bash
Download code
Copy code
php -m | grep soap
To check via your Laravel App (Web Server):
The web server (like PHP-FPM or Apache) might use a different
php.ini
file than your CLI. To be certain, temporarily add this to a route in your
routes/web.php
file and visit it in your browser:
PHP
Download code
Copy code
Route::get(
'/check-soap'
,
function
(
)
{
dd(extension_loaded(
'soap'
));
});
If this returns
true
, your application has access to the vulnerable extension.
2. Check Your PHP Version
2. Check Your PHP Version
If the SOAP extension is enabled, you must check if your PHP version falls within the vulnerable ranges mentioned in the CVE (e.g., versions below 8.2.31, 8.3.31, 8.4.21, or 8.5.6).
In the CLI:
Bash
Download code
Copy code
php -v
In your Laravel App:
PHP
Download code
Copy code
Route::get(
'/check-php'
,
function
(
)
{
dd(phpversion());
});
3. How to Secure Your Environment
3. How to Secure Your Environment
If you are running a vulnerable version of PHP and have the SOAP extension enabled, you have two primary options:
Option A: Update PHP (Recommended)
The best approach is to update your server's PHP binary to a patched version. How you do this depends on your hosting environment:
Laravel Sail / Docker:
Modify the PHP version referenced in your
docker-compose.yml
or Dockerfile, then rebuild your containers using
sail build --no-cache
.
Laravel Forge / Vapor:
Use the respective dashboards to upgrade the PHP version running on your servers or serverless environments.
Ubuntu / Debian Server:
Run standard package manager updates (e.g.,
sudo apt-get update && sudo apt-get upgrade php8.x-soap
).
Option B: Disable the SOAP Extension (Workaround)
If your application does not actually rely on SOAP (for example, if it only uses standard REST APIs), you can completely eliminate the attack surface by disabling the extension.
Find your loaded
php.ini
file by running
php --ini
.
Open the file and locate the line
extension=soap
(or
extension=php_soap.dll
on Windows).
Comment it out by adding a semicolon to the start of the line:
;extension=soap
.
Restart your web server or PHP-FPM service (e.g.,
sudo systemctl restart php8.2-fpm
).
Good response
Bad response
Share & export
Copy
Show more options
Show the uploaded image in a lightbox
Copy prompt
Edit
You said I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
You said
I don't understand what should be done. The task is address BE vulnerabilities and there are some vanta links. What should be done backend wise
Expand
Listen
Show thinking
Gemini said
Gemini said
It makes complete sense why you are confused! You were assigned a task to fix "Backend (BE) vulnerabilities" in your Laravel app, but the screenshot you provided is actually flagging a
JavaScript/Node.js vulnerability
, not a PHP one.
The image shows an alert for
npm-elliptic <= 6.6.1
, which is an
npm
(Node Package Manager) dependency. In modern Laravel applications,
npm
is typically used to manage frontend assets and build tools (like Vite or Laravel Mix), rather than backend PHP code (which uses Composer).
Here is exactly what you need to do to resolve this issue in your project:
1. Locate the Repository
1. Locate the Repository
The Vanta dashboard indicates this vulnerability is in a repository or project named
extension-app
. You need to open your terminal and navigate to the root directory of this specific project where the
package.json
file lives.
2. Identify How the Package is Used
2. Identify How the Package is Used
The package
elliptic
might be something your team installed directly, or (more likely) it is a "transitive dependency"—meaning another package you use relies on it.
Run this command in your terminal to see how it's being required:
Bash
Download code
Copy code
npm ls elliptic
This will output a tree showing exactly which package is bringing in the vulnerable version of
elliptic
....
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
32418
|
|
74311
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New)
Jiminny (New)
Platform Team
Platform Team
Add people
Add people
Board actions
Board actions
Share
Automation
Give feedback
Give feedback
Enter full screen
Enter full screen
Summary
Summary
Timeline
Timeline
Backlog
Backlog
Tab options
Tab options
Active sprints
Active sprints
Calendar
Calendar
Reports
Reports
Testing Board
Testing Board
List
List
Forms
Forms
Components
Components
Development
Development
Code
Code
Security
Security
Releases
Releases
Deployments
Deployments
Archived work items
Archived work items
Docs
Docs
Shortcuts
Shortcuts
Slack integration
Slack integration
Reporting Center
Reporting Center
Add to navigation
As you type to search or apply filters, the board updates with work items to match.
Search on current page
Filter by assignee
Filter assignees by Lukas Kovalik
Filter assignees by Aneliya Angelova
Filter assignees by Nikolay Ivanov
Filter assignees by Nikolay Nikolov
Filter assignees by Nikolay Yankov
Filter assignees by Steliyan Georgiev
Filter assignees by Unassigned
Epic
Epic
Type
Type
Quick filters
Quick filters
Complete sprint
Complete sprint
Sprint details
Sprint details
Group by Queries
Group
: Queries
Sprint insights
Sprint insights
View settings
View settings
More actions
More actions
Ready For DEV
READY FOR DEV
1
JY-19958 Upgrade BE libraries - May. Use the enter key to load the work item.
Upgrade BE libraries - May
MAINTENANCE
Backlog...
|
Firefox
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira — Work...
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
74311
|
|
74312
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New)
Jiminny (New)
Platform Team
Platform Team
Add people
Add people
Board actions
Board actions
Share
Automation
Give feedback
Give feedback
Enter full screen
Enter full screen
Summary
Summary
Timeline
Timeline
Backlog
Backlog
Tab options
Tab options
Active sprints
Active sprints
Calendar
Calendar
Reports
Reports
Testing Board
Testing Board
List
List
Forms
Forms
Components
Components
Development
Development
Code
Code
Security
Security
Releases
Releases
Deployments
Deployments
Archived work items
Archived work items
Docs
Docs
Shortcuts
Shortcuts
Slack integration
Slack integration
Reporting Center
Reporting Center
Add to navigation
As you type to search or apply filters, the board updates with work items to match.
Search on current page
Filter by assignee
Filter assignees by Lukas Kovalik
Filter assignees by Aneliya Angelova
Filter assignees by Nikolay Ivanov
Filter assignees by Nikolay Nikolov
Filter assignees by Nikolay Yankov
Filter assignees by Steliyan Georgiev
Filter assignees by Unassigned
Epic
Epic
Type
Type
Quick filters
Quick filters
Complete sprint
Complete sprint
Sprint details
Sprint details
Group by Queries
Group
: Queries
Sprint insights
Sprint insights
View settings
View settings
More actions
More actions
Ready For DEV
READY FOR DEV
1
JY-19958 Upgrade BE libraries - May. Use the enter key to load the work item.
Upgrade BE libraries - May
MAINTENANCE
Backlog
JY-19958
JY-19958
1
In DEV
IN DEV
2
JY-20833 MCP > Enable users to get a list of calls and their details. Use the enter key to load the work item.
MCP > Enable users to get a list of calls and their details
JIMINNY MCP CONNECTOR
In Dev
JY-20833
JY-20833
9
JY-20963 Fix foreign key violation when matching activities to deleted Salesforce opportunities. Use the enter key to load the work item.
Fix foreign key violation when matching activities to deleted Salesforce opportunities
Support tickets, Edit Parent...
|
Firefox
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira — Work...
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
74312
|
|
74313
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New)
Jiminny (New)
Platform Team
Platform Team
Add people
Add people
Board actions
Board actions
Share
Automation
Give feedback
Give feedback
Enter full screen
Enter full screen
Summary
Summary
Timeline
Timeline
Backlog
Backlog
Tab options
Tab options
Active sprints
Active sprints
Calendar
Calendar
Reports
Reports
Testing Board
Testing Board
List
List
Forms
Forms
Components
Components
Development
Development
Code
Code
Security
Security
Releases
Releases
Deployments
Deployments
Archived work items
Archived work items
Docs
Docs
Shortcuts
Shortcuts
Slack integration
Slack integration
Reporting Center
Reporting Center
Add to navigation
Open Rovo Chat
Open Rovo Chat...
|
Firefox
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira — Work...
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
74313
|
|
74314
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New)
Jiminny (New)
Platform Team
Platform Team
Add people
Add people
Board actions
Board actions
Share
Automation
Give feedback
Give feedback
Enter full screen
Enter full screen
Summary
Summary
Timeline
Timeline
Backlog
Backlog
Tab options
Tab options
Active sprints
Active sprints
Calendar
Calendar
Reports
Reports
Testing Board
Testing Board
List
List
Forms
Forms
Components
Components
Development
Development
Code
Code
Security
Security
Releases
Releases
Deployments
Deployments
Archived work items
Archived work items
Docs
Docs
Shortcuts
Shortcuts
Slack integration
Slack integration
Reporting Center
Reporting Center
Add to navigation
Results will be filtered below as you type to search or apply filters.
Search on current page
Filter by assignee
Filter assignees by Lukas Kovalik
Filter assignees by Ahmet Katranci
Filter assignees by Aneliya Angelova
Filter assignees by Galya Dimitrova
Filter assignees by George Tulev
Filter assignees by James Graham
+8
+8
Version
Version
Epic
Epic
Type
Type
Label
Label
Quick filters
Quick filters
Backlog insights
Backlog insights
View settings
View settings
More actions
More actions
Select all work items in sprint Platform Sprint 4 Q2
Platform Sprint 4 Q2 13 May – 26 May (22 work items)
Collapse
Collapse
Platform Sprint 4 Q2
Platform Sprint 4 Q2
13 May – 26 May
(22 work items)
Platform Sprint 4 Q2
22 work items
Not started (leftmost column): 1 of 44.5 (days)
In progress: 16 of 44.5 (days)
Completed (rightmost column): 27.5 of 44.5 (days)
Complete sprint
Complete sprint
Platform Sprint 4 Q2 actions
Platform Sprint 4 Q2 actions
- Upgrade php to 8.5 and release the changes to production - Make a good progress on the MCP implementation - the AI should know the user's details at a minimum; and we can test if the AI can use the information about the Jiminny's calls to answer questions about them
More actions Open workload by assignee summary modal
Open workload by assignee summary modal
JY-20361 AJ Panorama for Call Scoring in OD. Use the enter key to load the work item
JY-20361 AJ Panorama for Call Scoring in OD
JY-20361
AJ Panorama for Call Scoring in OD
AJ Panorama for Call Scoring in OD
AUTOMATED AI SCORING
status
DEPLOYED
2.5
JY-20725 [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts. Use the enter key to load the work item
JY-20725 [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts
JY-20725
[HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts
[HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts
PLATFORM STABILITY
status
DEPLOYED
4
JY-18091 Upgrade to PHP 8.5. Use the enter key to load the work item
JY-18091 Upgrade to PHP 8.5
JY-18091
Upgrade to PHP 8.5
Upgrade to PHP 8.5
PHP 8.5 UPGRADE
status
DEPLOYED
4
JY-20846 MCP > Enable the AI to know details about the user. Use the enter key to load the work item
JY-20846 MCP > Enable the AI to know details about the user
JY-20846
MCP > Enable the AI to know details about the user
MCP > Enable the AI to know details about the user
JIMINNY MCP CONNECTOR
status
IN QA
2
JY-20833 MCP > Enable users to get a list of calls and their details. Use the enter key to load the work item
JY-20833 MCP > Enable users to get a list of calls and their details
JY-20833
MCP > Enable users to get a list of calls and their details
MCP > Enable users to get a list of calls and their details
JIMINNY MCP CONNECTOR
status
IN DEV
9
JY-20835 MCP > Enable users to get a list of deals and their details. Use the enter key to load the work item
JY-20835 MCP > Enable users to get a list of deals and their details
JY-20835
MCP > Enable users to get a list of deals and their details
MCP > Enable users to get a list of deals and their details
JIMINNY MCP CONNECTOR
status
IN QA
5
JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report. Use the enter key to load the work item
JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report
JY-20676
Notify the user if a Panorama prompts is deleted but is used in AJ Report
Notify the user if a Panorama prompts is deleted but is used in AJ Report
AJ REPORTS
status
DEPLOYED
2.5
JY-20615 Notify the user if a SS is deleted but is used in AJ Report. Use the enter key to load the work item
JY-20615 Notify the user if a SS is deleted but is used in AJ Report
JY-20615
Notify the user if a SS is deleted but is used in AJ Report
Notify the user if a SS is deleted but is used in AJ Report
AJ REPORTS
status
DEPLOYED
2
JY-19958 Upgrade BE libraries - May. Use the enter key to load the work item
JY-19958 Upgrade BE libraries - May
JY-19958
Upgrade BE libraries - May
Upgrade BE libraries - May
MAINTENANCE
status
BACKLOG
1
JY-20613 Allow owner's role to be selected when setting up a trial. Use the enter key to load the work item
JY-20613 Allow owner's role to be selected when setting up a trial
JY-20613...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
74314
|
|
74315
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New)
Jiminny (New)
Platform Team
Platform Team
Add people
Add people
Board actions
Board actions
Share
Automation
Give feedback
Give feedback
Enter full screen
Enter full screen
Summary
Summary
Timeline
Timeline
Backlog
Backlog
Tab options
Tab options
Active sprints
Active sprints
Calendar
Calendar
Reports
Reports
Testing Board
Testing Board
List
List
Forms
Forms
Components
Components
Development
Development
Code
Code
Security
Security
Releases
Releases
Deployments
Deployments
Archived work items
Archived work items
Docs
Docs
Shortcuts
Shortcuts
Slack integration
Slack integration
Reporting Center
Reporting Center
Add to navigation
Results will be filtered below as you type to search or apply filters.
Search on current page
Filter by assignee
Filter assignees by Lukas Kovalik
Filter assignees by Ahmet Katranci
Filter assignees by Aneliya Angelova
Filter assignees by Galya Dimitrova
Filter assignees by George Tulev
Filter assignees by James Graham
+8
+8
Version
Version
Epic
Epic
Type
Type
Label
Label
Quick filters
Quick filters
Backlog insights
Backlog insights
View settings
View settings
More actions
More actions
Select all work items in sprint Platform Sprint 4 Q2
Platform Sprint 4 Q2 13 May – 26 May (22 work items)
Collapse
Collapse
Platform Sprint 4 Q2
Platform Sprint 4 Q2
13 May – 26 May
(22 work items)
Platform Sprint 4 Q2
22 work items
Not started (leftmost column): 1 of 44.5 (days)
In progress: 16 of 44.5 (days)
Completed (rightmost column): 27.5 of 44.5 (days)
Complete sprint
Complete sprint
Platform Sprint 4 Q2 actions
Platform Sprint 4 Q2 actions
- Upgrade php to 8.5 and release the changes to production - Make a good progress on the MCP implementation - the AI should know the user's details at a minimum; and we can test if the AI can use the information about the Jiminny's calls to answer questions about them
More actions Open workload by assignee summary modal
Open workload by assignee summary modal
JY-20361 AJ Panorama for Call Scoring in OD. Use the enter key to load the work item
JY-20361 AJ Panorama for Call Scoring in OD
JY-20361
AJ Panorama for Call Scoring in OD
AJ Panorama for Call Scoring in OD
AUTOMATED AI SCORING
status
DEPLOYED
2.5
JY-20725 [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts. Use the enter key to load the work item
JY-20725 [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts
JY-20725
[HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts
[HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts
PLATFORM STABILITY
status
DEPLOYED
4
JY-18091 Upgrade to PHP 8.5. Use the enter key to load the work item
JY-18091 Upgrade to PHP 8.5
JY-18091
Upgrade to PHP 8.5
Upgrade to PHP 8.5
PHP 8.5 UPGRADE
status
DEPLOYED
4
JY-20846 MCP > Enable the AI to know details about the user. Use the enter key to load the work item
JY-20846 MCP > Enable the AI to know details about the user
JY-20846
MCP > Enable the AI to know details about the user
MCP > Enable the AI to know details about the user
JIMINNY MCP CONNECTOR
status
IN QA
2
JY-20833 MCP > Enable users to get a list of calls and their details. Use the enter key to load the work item
JY-20833 MCP > Enable users to get a list of calls and their details
JY-20833
MCP > Enable users to get a list of calls and their details
MCP > Enable users to get a list of calls and their details
JIMINNY MCP CONNECTOR
status
IN DEV
9
JY-20835 MCP > Enable users to get a list of deals and their details. Use the enter key to load the work item
JY-20835 MCP > Enable users to get a list of deals and their details
JY-20835
MCP > Enable users to get a list of deals and their details
MCP > Enable users to get a list of deals and their details
JIMINNY MCP CONNECTOR
status
IN QA
5
JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report. Use the enter key to load the work item
JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report
JY-20676
Notify the user if a Panorama prompts is deleted but is used in AJ Report
Notify the user if a Panorama prompts is deleted but is used in AJ Report
AJ REPORTS
status
DEPLOYED
2.5
JY-20615 Notify the user if a SS is deleted but is used in AJ Report. Use the enter key to load the work item
JY-20615 Notify the user if a SS is deleted but is used in AJ Report
JY-20615
Notify the user if a SS is deleted but is used in AJ Report
Notify the user if a SS is deleted but is used in AJ Report
AJ REPORTS
status
DEPLOYED
2
JY-19958 Upgrade BE libraries - May. Use the enter key to load the work item
JY-19958 Upgrade BE libraries - May
JY-19958
Upgrade BE libraries - May
Upgrade BE libraries - May
MAINTENANCE
status
BACKLOG
1
JY-20613 Allow owner's role to be selected when setting up a trial. Use the enter key to load the work item
JY-20613 Allow owner's role to be selected when setting up a trial
JY-20613
Allow owner's role to be selected when setting up a trial
Allow owner's role to be selected when setting up a trial
IMPROVEMENT OF OUR EFFICIENCY
status
DEPLOYED
1.5
JY-20880 [Deadline 25 May] Migrate depricated Gemini 3.1 Flash Lite Preview model. Use the enter key to load the work item
JY-20880 [Deadline 25 May] Migrate depricated Gemini 3.1 Flash Lite Preview model
JY-20880
[Deadline 25 May] Migrate depricated Gemini 3.1 Flash Lite Preview model
[Deadline 25 May] Migrate depricated Gemini 3.1 Flash Lite Preview model
MAINTENANCE
status
DEPLOYED
1
JY-19951 Setup test coverage for Prophet in Sonar. Use the enter key to load the work item
JY-19951 Setup test coverage for Prophet in Sonar
JY-19951
Setup test coverage for Prophet in Sonar
Setup test coverage for Prophet in Sonar
MAINTENANCE
status
DEPLOYED
1
JY-20410 Improve Activity Type suggestions. Use the enter key to load the work item
JY-20410 Improve Activity Type suggestions
JY-20410
Improve Activity Type suggestions
Improve Activity Type suggestions
AUTO-DETECTED ACTIVITY TYPE...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
74315
|
|
74316
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New)
Jiminny (New)
Platform Team
Platform Team
Add people
Add people
Board actions
Board actions
Share
Automation
Give feedback
Give feedback
Enter full screen
Enter full screen
Summary
Summary
Timeline
Timeline
Backlog
Backlog
Active sprints
Active sprints
Calendar
Calendar
Reports
Reports
Testing Board
Testing Board
List
List
Forms
Forms
Components
Components
Development
Development
Code
Code
Security
Security
Releases
Releases
Deployments
Deployments
Archived work items
Archived work items
Docs
Docs
Shortcuts
Shortcuts
Slack integration
Slack integration
Reporting Center
Reporting Center
Add to navigation
Results will be filtered below as you type to search or apply filters.
Search on current page
Filter by assignee
Filter assignees by Lukas Kovalik
Filter assignees by Ahmet Katranci
Filter assignees by Aneliya Angelova
Filter assignees by Galya Dimitrova
Filter assignees by George Tulev
Filter assignees by James Graham
+8
+8
Version
Version
Epic
Epic
Type
Type
Label
Label
Quick filters
Quick filters
Backlog insights
Backlog insights
View settings
View settings
More actions
More actions
Select all work items in sprint Platform Sprint 4 Q2
Platform Sprint 4 Q2 13 May – 26 May (22 work items)
Collapse
Collapse
Platform Sprint 4 Q2
Platform Sprint 4 Q2
13 May – 26 May
(22 work items)
Platform Sprint 4 Q2
22 work items
Not started (leftmost column): 1 of 44.5 (days)
In progress: 16 of 44.5 (days)
Completed (rightmost column): 27.5 of 44.5 (days)
Complete sprint
Complete sprint
Platform Sprint 4 Q2 actions
Platform Sprint 4 Q2 actions
- Upgrade php to 8.5 and release the changes to production - Make a good progress on the MCP implementation - the AI should know the user's details at a minimum; and we can test if the AI can use the information about the Jiminny's calls to answer questions about them
More actions Open workload by assignee summary modal
Open workload by assignee summary modal
JY-20361 AJ Panorama for Call Scoring in OD. Use the enter key to load the work item
JY-20361 AJ Panorama for Call Scoring in OD
JY-20361
AJ Panorama for Call Scoring in OD
AJ Panorama for Call Scoring in OD
AUTOMATED AI SCORING
status
DEPLOYED
2.5
JY-20725 [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts. Use the enter key to load the work item
JY-20725 [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts
JY-20725
[HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts
[HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts
PLATFORM STABILITY
status
DEPLOYED
4
JY-18091 Upgrade to PHP 8.5. Use the enter key to load the work item
JY-18091 Upgrade to PHP 8.5
JY-18091
Upgrade to PHP 8.5
Upgrade to PHP 8.5
PHP 8.5 UPGRADE
status
DEPLOYED
4
JY-20846 MCP > Enable the AI to know details about the user. Use the enter key to load the work item
JY-20846 MCP > Enable the AI to know details about the user
JY-20846
MCP > Enable the AI to know details about the user
MCP > Enable the AI to know details about the user...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
74316
|
|
74317
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New)
Jiminny (New)
Platform Team
Platform Team
Add people
Add people
Board actions
Board actions
Share
Automation
Give feedback
Give feedback
Enter full screen
Enter full screen
Summary
Summary
Timeline
Timeline
Backlog
Backlog
Active sprints
Active sprints
Calendar
Calendar
Reports
Reports
Testing Board
Testing Board
List
List
Forms
Forms
Components
Components
Development
Development
Code
Code
Security
Security
Releases
Releases
Deployments
Deployments
Archived work items
Archived work items
Docs
Docs
Shortcuts
Shortcuts
Slack integration
Slack integration
Reporting Center
Reporting Center
Add to navigation
Results will be filtered below as you type to search or apply filters.
Search on current page
Filter by assignee
Filter assignees by Lukas Kovalik
Filter assignees by Ahmet Katranci
Filter assignees by Aneliya Angelova
Filter assignees by Galya Dimitrova
Filter assignees by George Tulev
Filter assignees by James Graham
+8
+8...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
74317
|
|
74318
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New)
Jiminny (New)
Platform Team
Platform Team
Add people
Add people
Board actions
Board actions
Share
Automation
Give feedback
Give feedback
Enter full screen
Enter full screen
Summary
Summary
Timeline
Timeline
Backlog
Backlog
Active sprints
Active sprints
Calendar
Calendar
Reports
Reports
Testing Board
Testing Board
List
List
Forms
Forms
Components
Components
Development
Development
Code
Code
Security
Security
Releases
Releases
Deployments
Deployments
Archived work items
Archived work items
Docs
Docs
Shortcuts
Shortcuts
Slack integration
Slack integration
Reporting Center
Reporting Center
Add to navigation
Results will be filtered below as you type to search or apply filters.
Search on current page
Filter by assignee
Filter assignees by Lukas Kovalik
Filter assignees by Ahmet Katranci
Filter assignees by Aneliya Angelova
Filter assignees by Galya Dimitrova
Filter assignees by George Tulev
Filter assignees by James Graham
+8
+8
Version
Version
Epic
Epic
Type
Type
Label
Label
Quick filters
Quick filters
Backlog insights
Backlog insights
View settings
View settings
More actions
More actions
Select all work items in sprint Platform Sprint 4 Q2
Platform Sprint 4 Q2 13 May – 26 May (22 work items)
Collapse
Collapse
Platform Sprint 4 Q2
Platform Sprint 4 Q2
13 May – 26 May
(22 work items)
Platform Sprint 4 Q2
22 work items
Not started (leftmost column): 1 of 44.5 (days)
In progress: 16 of 44.5 (days)
Completed (rightmost column): 27.5 of 44.5 (days)
Complete sprint
Complete sprint
Platform Sprint 4 Q2 actions
Platform Sprint 4 Q2 actions
- Upgrade php to 8.5 and release the changes to production - Make a good progress on the MCP implementation - the AI should know the user's details at a minimum; and we can test if the AI can use the information about the Jiminny's calls to answer questions about them
More actions Open workload by assignee summary modal
Open workload by assignee summary modal
JY-20846 MCP > Enable the AI to know details about the user. Use the enter key to load the work item
JY-20846 MCP > Enable the AI to know details about the user...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
74318
|
|
74319
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New)
Jiminny (New)
Platform Team
Platform Team
Add people
Add people
Board actions
Board actions
Share
Automation
Give feedback
Give feedback
Enter full screen
Enter full screen
Summary
Summary
Timeline
Timeline
Backlog
Backlog
Active sprints
Active sprints
Calendar
Calendar
Reports
Reports
Testing Board
Testing Board
List
List
Forms
Forms
Components
Components
Development
Development
Code
Code
Security
Security
Releases
Releases
Deployments
Deployments
Archived work items
Archived work items
Docs
Docs
Shortcuts
Shortcuts
Slack integration
Slack integration
Reporting Center
Reporting Center
Add to navigation
Results will be filtered below as you type to search or apply filters.
Search on current page
Filter by assignee
Filter assignees by Lukas Kovalik
Filter assignees by Ahmet Katranci
Filter assignees by Aneliya Angelova
Filter assignees by Galya Dimitrova
Filter assignees by George Tulev
Filter assignees by James Graham
+8
+8
Version
Version
Epic
Epic
Type
Type
Label
Label
Quick filters
Quick filters
Backlog insights
Backlog insights
View settings
View settings
More actions
More actions
Select all work items in sprint Platform Sprint 4 Q2
Platform Sprint 4 Q2 13 May – 26 May (22 work items)
Collapse
Collapse
Platform Sprint 4 Q2
Platform Sprint 4 Q2
13 May – 26 May
(22 work items)
Platform Sprint 4 Q2
22 work items
Not started (leftmost column): 1 of 44.5 (days)
In progress: 16 of 44.5 (days)
Completed (rightmost column): 27.5 of 44.5 (days)
Complete sprint
Complete sprint
Platform Sprint 4 Q2 actions
Platform Sprint 4 Q2 actions
- Upgrade php to 8.5 and release the changes to production - Make a good progress on the MCP implementation - the AI should know the user's details at a minimum; and we can test if the AI can use the information about the Jiminny's calls to answer questions about them
More actions Open workload by assignee summary modal
Open workload by assignee summary modal
JY-20833 MCP > Enable users to get a list of calls and their details. Use the enter key to load the work item
JY-20833 MCP > Enable users to get a list of calls and their details
JY-20833
MCP > Enable users to get a list of calls and their details
MCP > Enable users to get a list of calls and their details
JIMINNY MCP CONNECTOR
status
IN DEV
9
JY-20835 MCP > Enable users to get a list of deals and their details. Use the enter key to load the work item
JY-20835 MCP > Enable users to get a list of deals and their details
JY-20835
MCP > Enable users to get a list of deals and their details
MCP > Enable users to get a list of deals and their details
JIMINNY MCP CONNECTOR
status
IN QA
5
JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report. Use the enter key to load the work item
JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report
JY-20676
Notify the user if a Panorama prompts is deleted but is used in AJ Report
Notify the user if a Panorama prompts is deleted but is used in AJ Report
AJ REPORTS
status
DEPLOYED
2.5
JY-20615 Notify the user if a SS is deleted but is used in AJ Report. Use the enter key to load the work item
JY-20615 Notify the user if a SS is deleted but is used in AJ Report
JY-20615
Notify the user if a SS is deleted but is used in AJ Report...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
74319
|
|
74320
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New)
Jiminny (New)
Platform Team
Platform Team
Add people
Add people
Board actions
Board actions
Share
Automation
Give feedback
Give feedback
Enter full screen
Enter full screen
Summary
Summary
Timeline
Timeline
Backlog
Backlog
Active sprints
Active sprints
Calendar
Calendar
Reports
Reports
Testing Board
Testing Board
List
List
Forms
Forms
Components
Components
Development
Development
Code
Code
Security
Security
Releases
Releases
Deployments
Deployments
Archived work items
Archived work items
Docs
Docs
Shortcuts
Shortcuts
Slack integration
Slack integration
Reporting Center
Reporting Center
Add to navigation
Results will be filtered below as you type to search or apply filters.
Search on current page
Filter by assignee
Filter assignees by Lukas Kovalik
Filter assignees by Ahmet Katranci
Filter assignees by Aneliya Angelova
Filter assignees by Galya Dimitrova
Filter assignees by George Tulev
Filter assignees by James Graham
+8
+8
Version
Version
Epic
Epic
Type
Type
Label
Label
Quick filters
Quick filters
Backlog insights
Backlog insights
View settings
View settings
More actions
More actions
Select all work items in sprint Platform Sprint 4 Q2
Platform Sprint 4 Q2 13 May – 26 May (22 work items)
Collapse
Collapse
Platform Sprint 4 Q2
Platform Sprint 4 Q2
13 May – 26 May
(22 work items)
Platform Sprint 4 Q2
22 work items
Not started (leftmost column): 1 of 44.5 (days)
In progress: 16 of 44.5 (days)
Completed (rightmost column): 27.5 of 44.5 (days)
Complete sprint
Complete sprint
Platform Sprint 4 Q2 actions
Platform Sprint 4 Q2 actions
- Upgrade php to 8.5 and release the changes to production - Make a good progress on the MCP implementation - the AI should know the user's details at a minimum; and we can test if the AI can use the information about the Jiminny's calls to answer questions about them
More actions Open workload by assignee summary modal
Open workload by assignee summary modal
JY-20833 MCP > Enable users to get a list of calls and their details. Use the enter key to load the work item
JY-20833 MCP > Enable users to get a list of calls and their details
JY-20833
MCP > Enable users to get a list of calls and their details
MCP > Enable users to get a list of calls and their details
JIMINNY MCP CONNECTOR
status
IN DEV
9
JY-20835 MCP > Enable users to get a list of deals and their details. Use the enter key to load the work item
JY-20835 MCP > Enable users to get a list of deals and their details
JY-20835
MCP > Enable users to get a list of deals and their details
MCP > Enable users to get a list of deals and their details
JIMINNY MCP CONNECTOR
status
IN QA
5
JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report. Use the enter key to load the work item
JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report
JY-20676
Notify the user if a Panorama prompts is deleted but is used in AJ Report
Notify the user if a Panorama prompts is deleted but is used in AJ Report
AJ REPORTS
status
DEPLOYED
2.5
JY-20615 Notify the user if a SS is deleted but is used in AJ Report. Use the enter key to load the work item
JY-20615 Notify the user if a SS is deleted but is used in AJ Report
JY-20615
Notify the user if a SS is deleted but is used in AJ Report
Notify the user if a SS is deleted but is used in AJ Report
AJ REPORTS
status
DEPLOYED
2
JY-19958 Upgrade BE libraries - May. Use the enter key to load the work item
JY-19958 Upgrade BE libraries - May
JY-19958
Upgrade BE libraries - May
Upgrade BE libraries - May
MAINTENANCE
status
BACKLOG
1
JY-20613 Allow owner's role to be selected when setting up a trial. Use the enter key to load the work item
JY-20613 Allow owner's role to be selected when setting up a trial
JY-20613
Allow owner's role to be selected when setting up a trial
Allow owner's role to be selected when setting up a trial
IMPROVEMENT OF OUR EFFICIENCY
status
DEPLOYED
1.5
JY-20880 [Deadline 25 May] Migrate depricated Gemini 3.1 Flash Lite Preview model. Use the enter key to load the work item
JY-20880 [Deadline 25 May] Migrate depricated Gemini 3.1 Flash Lite Preview model
JY-20880
[Deadline 25 May] Migrate depricated Gemini 3.1 Flash Lite Preview model
[Deadline 25 May] Migrate depricated Gemini 3.1 Flash Lite Preview model
MAINTENANCE
status
DEPLOYED
1
JY-19951 Setup test coverage for Prophet in Sonar. Use the enter key to load the work item
JY-19951 Setup test coverage for Prophet in Sonar
JY-19951
Setup test coverage for Prophet in Sonar
Setup test coverage for Prophet in Sonar
Setup test coverage for Prophet in Sonar
Maintenance
MAINTENANCE
Deployed - Change status
DEPLOYED
Edit story point estimate, edit
1
Priority: Medium
Assignee: Steliyan Georgiev
More actions for JY-19951 Setup test coverage for Prophet in Sonar
More actions for JY-19951 Setup test coverage for Prophet in Sonar
JY-20410 Improve Activity Type suggestions. Use the enter key to load the work item
JY-20410 Improve Activity Type suggestions
JY-20410
Improve Activity Type suggestions
Improve Activity Type suggestions
Improve Activity Type suggestions
Auto-detected activity type
AUTO-DETECTED ACTIVITY TYPE
Deployed - Change status
DEPLOYED
Edit story point estimate, edit
2
Priority: Medium
Assignee: Steliyan Georgiev
More actions for JY-20410 Improve Activity Type suggestions
More actions for JY-20410 Improve Activity Type suggestions
JY-20881 Upgrade Python and libraries - May. Use the enter key to load the work item
JY-20881 Upgrade Python and libraries - May...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
74320
|
|
74321
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New)
Jiminny (New)
Platform Team
Platform Team
Add people
Add people
Board actions
Board actions
Share
Automation
Give feedback
Give feedback
Enter full screen
Enter full screen
Summary
Summary
Timeline
Timeline
Backlog
Backlog
Active sprints
Active sprints
Calendar
Calendar
Reports
Reports
Testing Board
Testing Board
List
List
Forms
Forms
Components
Components
Development
Development
Code
Code
Security
Security
Releases
Releases
Deployments
Deployments
Archived work items
Archived work items
Docs
Docs
Shortcuts
Shortcuts
Slack integration
Slack integration
Reporting Center
Reporting Center
Add to navigation
Results will be filtered below as you type to search or apply filters.
Search on current page
Filter by assignee
Filter assignees by Lukas Kovalik
Filter assignees by Ahmet Katranci
Filter assignees by Aneliya Angelova
Filter assignees by Galya Dimitrova
Filter assignees by George Tulev
Filter assignees by James Graham
+8
+8
Version
Version
Epic
Epic
Type
Type
Label
Label
Quick filters
Quick filters
Backlog insights
Backlog insights
View settings
View settings
More actions
More actions
Select all work items in sprint Platform Sprint 4 Q2
Platform Sprint 4 Q2 13 May – 26 May (22 work items)
Collapse
Collapse
Platform Sprint 4 Q2
Platform Sprint 4 Q2
13 May – 26 May
(22 work items)
Platform Sprint 4 Q2
22 work items
Not started (leftmost column): 1 of 44.5 (days)
In progress: 16 of 44.5 (days)
Completed (rightmost column): 27.5 of 44.5 (days)
Complete sprint
Complete sprint
Platform Sprint 4 Q2 actions
Platform Sprint 4 Q2 actions
- Upgrade php to 8.5 and release the changes to production - Make a good progress on the MCP implementation - the AI should know the user's details at a minimum; and we can test if the AI can use the information about the Jiminny's calls to answer questions about them
More actions Open workload by assignee summary modal
Open workload by assignee summary modal
JY-20833 MCP > Enable users to get a list of calls and their details. Use the enter key to load the work item
JY-20833 MCP > Enable users to get a list of calls and their details
JY-20833
MCP > Enable users to get a list of calls and their details
MCP > Enable users to get a list of calls and their details
JIMINNY MCP CONNECTOR
status
IN DEV
9
JY-20835 MCP > Enable users to get a list of deals and their details. Use the enter key to load the work item
JY-20835 MCP > Enable users to get a list of deals and their details
JY-20835
MCP > Enable users to get a list of deals and their details
MCP > Enable users to get a list of deals and their details
JIMINNY MCP CONNECTOR
status
IN QA
5
JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report. Use the enter key to load the work item
JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report
JY-20676
Notify the user if a Panorama prompts is deleted but is used in AJ Report
Notify the user if a Panorama prompts is deleted but is used in AJ Report
AJ REPORTS
status
DEPLOYED
2.5
JY-20615 Notify the user if a SS is deleted but is used in AJ Report. Use the enter key to load the work item
JY-20615 Notify the user if a SS is deleted but is used in AJ Report
JY-20615
Notify the user if a SS is deleted but is used in AJ Report
Notify the user if a SS is deleted but is used in AJ Report
AJ REPORTS
status
DEPLOYED
2
JY-19958 Upgrade BE libraries - May. Use the enter key to load the work item
JY-19958 Upgrade BE libraries - May
JY-19958
Upgrade BE libraries - May
Upgrade BE libraries - May
MAINTENANCE
status
BACKLOG
1
JY-20613 Allow owner's role to be selected when setting up a trial. Use the enter key to load the work item
JY-20613 Allow owner's role to be selected when setting up a trial
JY-20613
Allow owner's role to be selected when setting up a trial
Allow owner's role to be selected when setting up a trial
IMPROVEMENT OF OUR EFFICIENCY
status
DEPLOYED
1.5
JY-20880 [Deadline 25 May] Migrate depricated Gemini 3.1 Flash Lite Preview model. Use the enter key to load the work item
JY-20880 [Deadline 25 May] Migrate depricated Gemini 3.1 Flash Lite Preview model
JY-20880
[Deadline 25 May] Migrate depricated Gemini 3.1 Flash Lite Preview model
[Deadline 25 May] Migrate depricated Gemini 3.1 Flash Lite Preview model
MAINTENANCE
status
DEPLOYED
1
JY-19951 Setup test coverage for Prophet in Sonar. Use the enter key to load the work item
JY-19951 Setup test coverage for Prophet in Sonar
JY-19951
Setup test coverage for Prophet in Sonar
Setup test coverage for Prophet in Sonar
Setup test coverage for Prophet in Sonar
Maintenance
MAINTENANCE
Deployed - Change status
DEPLOYED
Edit story point estimate, edit...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
74321
|
|
74322
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New)
Jiminny (New)
Platform Team
Platform Team
Add people
Add people
Board actions
Board actions
Share
Automation
Give feedback
Give feedback
Enter full screen
Enter full screen
Summary
Summary
Timeline
Timeline
Backlog
Backlog
Active sprints
Active sprints
Calendar
Calendar
Reports
Reports
Testing Board
Testing Board
List
List
Forms
Forms
Components
Components
Development
Development
Code
Code
Security
Security
Releases
Releases
Deployments
Deployments
Archived work items
Archived work items
Docs
Docs
Shortcuts
Shortcuts
Slack integration
Slack integration
Reporting Center
Reporting Center
Add to navigation
Results will be filtered below as you type to search or apply filters.
Search on current page
Filter by assignee
Filter assignees by Lukas Kovalik
Filter assignees by Ahmet Katranci
Filter assignees by Aneliya Angelova
Filter assignees by Galya Dimitrova
Filter assignees by George Tulev
Filter assignees by James Graham
+8
+8
Version
Version
Epic
Epic
Type
Type
Label
Label
Quick filters
Quick filters
Backlog insights
Backlog insights
View settings
View settings
More actions
More actions
Select all work items in sprint Platform Sprint 4 Q2
Platform Sprint 4 Q2 13 May – 26 May (22 work items)
Collapse
Collapse
Platform Sprint 4 Q2
Platform Sprint 4 Q2
13 May – 26 May
(22 work items)
Platform Sprint 4 Q2
22 work items
Not started (leftmost column): 1 of 44.5 (days)
In progress: 16 of 44.5 (days)
Completed (rightmost column): 27.5 of 44.5 (days)
Complete sprint
Complete sprint
Platform Sprint 4 Q2 actions
Platform Sprint 4 Q2 actions
- Upgrade php to 8.5 and release the changes to production - Make a good progress on the MCP implementation - the AI should know the user's details at a minimum; and we can test if the AI can use the information about the Jiminny's calls to answer questions about them
More actions Open workload by assignee summary modal
Open workload by assignee summary modal
JY-20833 MCP > Enable users to get a list of calls and their details. Use the enter key to load the work item
JY-20833 MCP > Enable users to get a list of calls and their details
JY-20833
MCP > Enable users to get a list of calls and their details
MCP > Enable users to get a list of calls and their details
JIMINNY MCP CONNECTOR
status
IN DEV
9
JY-20835 MCP > Enable users to get a list of deals and their details. Use the enter key to load the work item
JY-20835 MCP > Enable users to get a list of deals and their details
JY-20835
MCP > Enable users to get a list of deals and their details
MCP > Enable users to get a list of deals and their details
JIMINNY MCP CONNECTOR
status
IN QA
5
JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report. Use the enter key to load the work item
JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report
JY-20676
Notify the user if a Panorama prompts is deleted but is used in AJ Report
Notify the user if a Panorama prompts is deleted but is used in AJ Report
AJ REPORTS
status
DEPLOYED
2.5
JY-20615 Notify the user if a SS is deleted but is used in AJ Report. Use the enter key to load the work item
JY-20615 Notify the user if a SS is deleted but is used in AJ Report
JY-20615
Notify the user if a SS is deleted but is used in AJ Report
Notify the user if a SS is deleted but is used in AJ Report
AJ REPORTS
status
DEPLOYED
2
JY-19958 Upgrade BE libraries - May. Use the enter key to load the work item
JY-19958 Upgrade BE libraries - May
JY-19958
Upgrade BE libraries - May
Upgrade BE libraries - May
MAINTENANCE
status
BACKLOG
1
JY-20613 Allow owner's role to be selected when setting up a trial. Use the enter key to load the work item
JY-20613 Allow owner's role to be selected when setting up a trial
JY-20613
Allow owner's role to be selected when setting up a trial...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
74322
|
|
74323
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New)
Jiminny (New)
Platform Team
Platform Team
Add people
Add people
Board actions
Board actions
Share
Automation
Give feedback
Give feedback
Enter full screen
Enter full screen
Summary
Summary
Timeline
Timeline
Backlog
Backlog
Active sprints
Active sprints
Calendar
Calendar
Reports
Reports
Testing Board
Testing Board
List
List
Forms
Forms
Components
Components
Development
Development
Code
Code
Security
Security
Releases
Releases
Deployments
Deployments
Archived work items
Archived work items
Docs
Docs
Shortcuts
Shortcuts
Slack integration
Slack integration
Reporting Center
Reporting Center
Add to navigation
Results will be filtered below as you type to search or apply filters.
Search on current page
Filter by assignee
Filter assignees by Lukas Kovalik
Filter assignees by Ahmet Katranci
Filter assignees by Aneliya Angelova
Filter assignees by Galya Dimitrova
Filter assignees by George Tulev
Filter assignees by James Graham
+8
+8
Version
Version
Epic
Epic
Type
Type
Label
Label
Quick filters
Quick filters
Backlog insights
Backlog insights
View settings
View settings
More actions
More actions
Select all work items in sprint Platform Sprint 4 Q2
Platform Sprint 4 Q2 13 May – 26 May (22 work items)
Collapse
Collapse
Platform Sprint 4 Q2
Platform Sprint 4 Q2
13 May – 26 May
(22 work items)
Platform Sprint 4 Q2
22 work items
Not started (leftmost column): 1 of 44.5 (days)
In progress: 16 of 44.5 (days)
Completed (rightmost column): 27.5 of 44.5 (days)
Complete sprint
Complete sprint
Platform Sprint 4 Q2 actions
Platform Sprint 4 Q2 actions
- Upgrade php to 8.5 and release the changes to production - Make a good progress on the MCP implementation - the AI should know the user's details at a minimum; and we can test if the AI can use the information about the Jiminny's calls to answer questions about them
More actions Open workload by assignee summary modal
Open workload by assignee summary modal
JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report. Use the enter key to load the work item
JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report
JY-20676
Notify the user if a Panorama prompts is deleted but is used in AJ Report
Notify the user if a Panorama prompts is deleted but is used in AJ Report
AJ REPORTS
status
DEPLOYED
2.5
JY-20615 Notify the user if a SS is deleted but is used in AJ Report. Use the enter key to load the work item
JY-20615 Notify the user if a SS is deleted but is used in AJ Report
JY-20615
Notify the user if a SS is deleted but is used in AJ Report
Notify the user if a SS is deleted but is used in AJ Report
AJ REPORTS
status
DEPLOYED
2
JY-19958 Upgrade BE libraries - May. Use the enter key to load the work item
JY-19958 Upgrade BE libraries - May
JY-19958
Upgrade BE libraries - May
Upgrade BE libraries - May
MAINTENANCE
status
BACKLOG
1
JY-20613 Allow owner's role to be selected when setting up a trial. Use the enter key to load the work item
JY-20613 Allow owner's role to be selected when setting up a trial
JY-20613
Allow owner's role to be selected when setting up a trial
Allow owner's role to be selected when setting up a trial
IMPROVEMENT OF OUR EFFICIENCY
status
DEPLOYED
1.5
JY-20880 [Deadline 25 May] Migrate depricated Gemini 3.1 Flash Lite Preview model. Use the enter key to load the work item
JY-20880 [Deadline 25 May] Migrate depricated Gemini 3.1 Flash Lite Preview model
JY-20880
[Deadline 25 May] Migrate depricated Gemini 3.1 Flash Lite Preview model
[Deadline 25 May] Migrate depricated Gemini 3.1 Flash Lite Preview model
MAINTENANCE
status
DEPLOYED
1
JY-19951 Setup test coverage for Prophet in Sonar. Use the enter key to load the work item
JY-19951 Setup test coverage for Prophet in Sonar
JY-19951...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
74323
|
|
74324
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New)
Jiminny (New)
Platform Team
Platform Team
Add people
Add people
Board actions
Board actions
Share
Automation
Give feedback
Give feedback
Enter full screen
Enter full screen
Summary
Summary
Timeline
Timeline
Backlog
Backlog
Active sprints
Active sprints
Calendar
Calendar
Reports
Reports
Testing Board
Testing Board
List
List
Forms
Forms
Components
Components
Development
Development
Code
Code
Security
Security
Releases
Releases
Deployments
Deployments
Archived work items
Archived work items
Docs
Docs
Shortcuts
Shortcuts
Slack integration
Slack integration
Reporting Center
Reporting Center
Add to navigation
Results will be filtered below as you type to search or apply filters.
Search on current page
Filter by assignee
Filter assignees by Lukas Kovalik
Filter assignees by Ahmet Katranci
Filter assignees by Aneliya Angelova
Filter assignees by Galya Dimitrova
Filter assignees by George Tulev
Filter assignees by James Graham
+8
+8
Version
Version
Epic
Epic
Type
Type
Label
Label
Quick filters
Quick filters
Backlog insights
Backlog insights
View settings
View settings
More actions
More actions
Select all work items in sprint Platform Sprint 4 Q2
Platform Sprint 4 Q2 13 May – 26 May (22 work items)
Collapse
Collapse
Platform Sprint 4 Q2
Platform Sprint 4 Q2
13 May – 26 May
(22 work items)
Platform Sprint 4 Q2
22 work items
Not started (leftmost column): 1 of 44.5 (days)
In progress: 16 of 44.5 (days)
Completed (rightmost column): 27.5 of 44.5 (days)
Complete sprint
Complete sprint
Platform Sprint 4 Q2 actions
Platform Sprint 4 Q2 actions
- Upgrade php to 8.5 and release the changes to production - Make a good progress on the MCP implementation - the AI should know the user's details at a minimum; and we can test if the AI can use the information about the Jiminny's calls to answer questions about them
More actions Open workload by assignee summary modal
Open workload by assignee summary modal
JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report. Use the enter key to load the work item...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
74324
|
|
74325
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New)
Jiminny (New)
Platform Team
Platform Team
Add people
Add people
Board actions
Board actions
Share
Automation
Give feedback
Give feedback
Enter full screen
Enter full screen
Summary
Summary
Timeline
Timeline
Backlog
Backlog
Active sprints
Active sprints
Calendar
Calendar
Reports
Reports
Testing Board
Testing Board
List
List
Forms
Forms
Components
Components
Development
Development
Code
Code
Security
Security
Releases
Releases
Deployments
Deployments
Archived work items
Archived work items
Docs
Docs
Shortcuts
Shortcuts
Slack integration
Slack integration
Reporting Center
Reporting Center
Add to navigation
Results will be filtered below as you type to search or apply filters.
Search on current page
Filter by assignee
Filter assignees by Lukas Kovalik
Filter assignees by Ahmet Katranci
Filter assignees by Aneliya Angelova
Filter assignees by Galya Dimitrova
Filter assignees by George Tulev
Filter assignees by James Graham
+8
+8
Version
Version
Epic
Epic
Type
Type
Label
Label
Quick filters
Quick filters
Backlog insights
Backlog insights
View settings
View settings
More actions
More actions
Select all work items in sprint Platform Sprint 4 Q2
Platform Sprint 4 Q2 13 May – 26 May (22 work items)
Collapse
Collapse
Platform Sprint 4 Q2
Platform Sprint 4 Q2
13 May – 26 May
(22 work items)
Platform Sprint 4 Q2
22 work items
Not started (leftmost column): 1 of 44.5 (days)
In progress: 16 of 44.5 (days)
Completed (rightmost column): 27.5 of 44.5 (days)
Complete sprint
Complete sprint
Platform Sprint 4 Q2 actions
Platform Sprint 4 Q2 actions
- Upgrade php to 8.5 and release the changes to production - Make a good progress on the MCP implementation - the AI should know the user's details at a minimum; and we can test if the AI can use the information about the Jiminny's calls to answer questions about them
More actions Open workload by assignee summary modal
Open workload by assignee summary modal
JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report. Use the enter key to load the work item
JY-20676 Notify the user if a Panorama prompts is deleted but is used in AJ Report
JY-20676
Notify the user if a Panorama prompts is deleted but is used in AJ Report
Notify the user if a Panorama prompts is deleted but is used in AJ Report
AJ REPORTS
status
DEPLOYED
2.5
JY-20615 Notify the user if a SS is deleted but is used in AJ Report. Use the enter key to load the work item
JY-20615 Notify the user if a SS is deleted but is used in AJ Report
JY-20615
Notify the user if a SS is deleted but is used in AJ Report
Notify the user if a SS is deleted but is used in AJ Report
AJ REPORTS
status
DEPLOYED
2
JY-19958 Upgrade BE libraries - May. Use the enter key to load the work item
JY-19958 Upgrade BE libraries - May
JY-19958
Upgrade BE libraries - May
Upgrade BE libraries - May
MAINTENANCE
status
BACKLOG
1
JY-20613 Allow owner's role to be selected when setting up a trial. Use the enter key to load the work item
JY-20613 Allow owner's role to be selected when setting up a trial
JY-20613
Allow owner's role to be selected when setting up a trial
Allow owner's role to be selected when setting up a trial
IMPROVEMENT OF OUR EFFICIENCY
status
DEPLOYED
1.5
JY-20880 [Deadline 25 May] Migrate depricated Gemini 3.1 Flash Lite Preview model. Use the enter key to load the work item
JY-20880 [Deadline 25 May] Migrate depricated Gemini 3.1 Flash Lite Preview model
JY-20880
[Deadline 25 May] Migrate depricated Gemini 3.1 Flash Lite Preview model
[Deadline 25 May] Migrate depricated Gemini 3.1 Flash Lite Preview model
MAINTENANCE
status
DEPLOYED
1
JY-19951 Setup test coverage for Prophet in Sonar. Use the enter key to load the work item
JY-19951 Setup test coverage for Prophet in Sonar
JY-19951
Setup test coverage for Prophet in Sonar
Setup test coverage for Prophet in Sonar...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/jira/software/c/projects/JY/ jiminny.atlassian.net/jira/software/c/projects/JY/boards/37/backlog...
|
74325
|