|
74399
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
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
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74399
|
|
74400
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
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
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74400
|
|
74401
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
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
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74401
|
|
74402
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
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
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities
Initial Owner/Profile Sync for Opportunities
Where It Happens
Where It Happens
Trigger:
ProfileCreated
event →
SyncProfileOpportunities
listener
Turn on wrap
Copy as text
1
User connects to CRM → Profile created → ProfileCreated event
2
↓
3
SyncProfileOpportunities::handle()
4
↓
5
SyncOpportunitiesJob dispatched
Location
Location
SyncProfileOpportunities.php
How It Works
How It Works
Step
Action
1
ProfileCreated
event fires when a new CRM profile is created...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74402
|
|
74403
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
Close tab
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
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74403
|
|
74404
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
Close tab
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
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74404
|
|
74405
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
Close tab
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
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities
Initial Owner/Profile Sync for Opportunities
Where It Happens
Where It Happens
Trigger:
ProfileCreated
event →
SyncProfileOpportunities
listener
Turn on wrap
Copy as text
1
User connects to CRM → Profile created → ProfileCreated event
2
↓
3
SyncProfileOpportunities::handle()
4
↓
5
SyncOpportunitiesJob dispatched
Location
Location
SyncProfileOpportunities.php
How It Works
How It Works
Step
Action
1
ProfileCreated
event fires when a new CRM profile is created
2
SyncProfileOpportunities
listener handles it
3
Dispatches
SyncOpportunitiesJob
with
crm_profile_id
parameter
4
Uses
LAST_MODIFIED_BY_PROFILE_SYNC_OPPORTUNITY_STRATEGY
Step
1
2
3
4
Action
ProfileCreated
event fires when a new CRM profile is created
SyncProfileOpportunities
listener handles it
Dispatches
SyncOpportunitiesJob
with
crm_profile_id
parameter
Uses
LAST_MODIFIED_BY_PROFILE_SYNC_OPPORTUNITY_STRATEGY
Providers Supported (lines 51-61)
Providers Supported (lines 51-61)
HubSpot
Salesforce
Batching?
Batching?
No batching
- Uses
SyncOpportunitiesJob
which calls
syncOpportunities()
:
Salesforce:
One-by-one (
importOpportunity()
in a loop)
HubSpot:
In-memory buffer of 800, but still processes via
processOpportunityBatch()
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
Resize work item view side panel
Watch options: You are not watching this issue, 2 people watching
2
Share
Share...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74405
|
|
74406
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
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
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74406
|
|
74407
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
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
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities
Initial Owner/Profile Sync for Opportunities
Where It Happens
Where It Happens
Trigger:
ProfileCreated
event →
SyncProfileOpportunities
listener
Turn on wrap
Copy as text
1
User connects to CRM → Profile created → ProfileCreated event
2
↓
3
SyncProfileOpportunities::handle()
4
↓
5
SyncOpportunitiesJob dispatched
Location
Location
SyncProfileOpportunities.php
How It Works
How It Works
Step
Action
1
ProfileCreated
event fires when a new CRM profile is created
2
SyncProfileOpportunities
listener handles it
3...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74407
|
|
74408
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
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
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities
Initial Owner/Profile Sync for Opportunities
Where It Happens
Where It Happens
Trigger:
ProfileCreated
event →
SyncProfileOpportunities
listener
Turn on wrap
Copy as text
1
User connects to CRM → Profile created → ProfileCreated event
2
↓
3
SyncProfileOpportunities::handle()
4
↓
5
SyncOpportunitiesJob dispatched
Location
Location...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74408
|
|
74409
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
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
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities
Initial Owner/Profile Sync for Opportunities
Where It Happens
Where It Happens
Trigger:
ProfileCreated
event →
SyncProfileOpportunities
listener
Turn on wrap
Copy as text
1
User connects to CRM → Profile created → ProfileCreated event
2
↓
3
SyncProfileOpportunities::handle()
4
↓
5
SyncOpportunitiesJob dispatched
Location
Location
SyncProfileOpportunities.php
How It Works
How It Works
Step
Action
1
ProfileCreated
event fires when a new CRM profile is created
2
SyncProfileOpportunities
listener handles it
3...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74409
|
|
74410
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
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
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74410
|
|
74411
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
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
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74411
|
|
74412
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
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
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74412
|
|
74413
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
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
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update......
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74413
|
|
74414
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
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
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74414
|
|
74415
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
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
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74415
|
|
74416
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
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
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74416
|
|
74417
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
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
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities
Initial Owner/Profile Sync for Opportunities
Where It Happens
Where It Happens
Trigger:
ProfileCreated
event →
SyncProfileOpportunities
listener
Turn on wrap...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74417
|
|
32521
|
Work item search - Jira
Work item search - Jira
[J Work item search - Jira
Work item search - Jira
[JY-20421] Update libs - Jira
[JY-20421] Update libs - 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...
|
Firefox
|
[JY-20421] Update libs - Jira — Work
|
jiminny.atlassian.net/browse/JY-20421
|
32521
|
|
32522
|
Work item search - Jira
Work item search - Jira
[J Work item search - Jira
Work item search - Jira
[JY-20421] Update libs - Jira
[JY-20421] Update libs - 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)...
|
Firefox
|
[JY-20421] Update libs - Jira — Work
|
jiminny.atlassian.net/browse/JY-20421
|
32522
|
|
32523
|
Work item search - Jira
Work item search - Jira
[J Work item search - Jira
Work item search - Jira
[JY-20421] Update libs - Jira
[JY-20421] Update libs - 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...
|
Firefox
|
[JY-20421] Update libs - Jira — Work
|
jiminny.atlassian.net/browse/JY-20421
|
32523
|
|
32547
|
Work item search - Jira
Work item search - Jira
Cl Work item search - Jira
Work item search - 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
)....
|
Firefox
|
Work item search - Jira — Work
|
jiminny.atlassian.net/browse/JY-19967?search_id=91 jiminny.atlassian.net/browse/JY-19967?search_id=91e0961a-9652-4c0d-bf2c-016738fc3f74&referrer=quick-find...
|
32547
|
|
32548
|
Work item search - Jira
Work item search - Jira
Cl Work item search - Jira
Work item search - 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(...
|
Firefox
|
Work item search - Jira — Work
|
jiminny.atlassian.net/browse/JY-19967?search_id=91 jiminny.atlassian.net/browse/JY-19967?search_id=91e0961a-9652-4c0d-bf2c-016738fc3f74&referrer=quick-find...
|
32548
|
|
32549
|
[JY-19967] Upgrade Python and libraries - Apr - Ji [JY-19967] Upgrade Python and libraries - Apr - Jira
[JY-19967] Upgrade Python and libraries - Apr - 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...
|
Firefox
|
[JY-19967] Upgrade Python and libraries - Apr - Ji [JY-19967] Upgrade Python and libraries - Apr - Jira — Work...
|
jiminny.atlassian.net/browse/JY-19967?search_id=91 jiminny.atlassian.net/browse/JY-19967?search_id=91e0961a-9652-4c0d-bf2c-016738fc3f74&referrer=quick-find...
|
32549
|
|
32747
|
SlackFileEditViewGoHistoryWindowHelppathnamesDOCKE SlackFileEditViewGoHistoryWindowHelppathnamesDOCKER: /home/jiminny/vendor/phpunit/phpunitphpunit/phpunitDEV (docker)supportissues : [URL_WITH_CREDENTIALS] lDEV (c)APP (-zsh•HomeDMsActivityFilesLater..•Morelthl§ Support Daily • in 2h 24 m100% (C478•Wed 13 May 12:36:09ED→QDescribe what you are looking forJiminny …..Nikolay Ivanov6 0cunoartylau# engineering# general# jiminny-bg# platform-tickets# product_launches# random# releases# sofia-office# support# thank-yous# the_people_of jimi...• Messages+Direct messages& Nikolay Ivanovdo James Graham. Stoyan Tanev®. Galya Dimitrova&. Steliyan GeorgievLo Petko Kashinski®. Aneliya Angelovaã. Stefka Stoyanova•. Vasil Vasilev 0!Lukas Kovalik y...AppsAdd canvasO FilesLukas Kovalik 11.Today ~мен все ме праща наhttps://app.vanta.com/c/jiminny.com/employee/onboardingNikolay Ivanov 11:01 AMХм, Джейс дали не може да ти помогне?Lukas Kovalik 11:01 AMще питам James, предполагам че нямам правада мерсиNikolay Ivanov 11:01 AMмдаМОЛЯLukas Kovalik 12:13 PMНики сори, още един въпрос имамкогато ги правеше ти FE ли оправяима vulnerabilities no npmNikolay Ivanov 12:28 PMнетях ги оставямLukas Kovalik 12:29 PMаз погледнах твоя тикет и там друго нямашесамо FEкак стигна до WorkerJira CloudMessage Nikolay IvanovToast...
|
Firefox
|
[JY-19967] Upgrade Python and libraries - Apr - Ji [JY-19967] Upgrade Python and libraries - Apr - Jira — Work...
|
jiminny.atlassian.net/browse/JY-19967?search_id=91 jiminny.atlassian.net/browse/JY-19967?search_id=91e0961a-9652-4c0d-bf2c-016738fc3f74&referrer=quick-find...
|
32747
|
|
32748
|
[JY-19967] Upgrade Python and libraries - Apr - Ji [JY-19967] Upgrade Python and libraries - Apr - Jira
[JY-19967] Upgrade Python and libraries - Apr - Jira
Close tab
Dependabot alerts · jiminny/prophet
Dependabot alerts · jiminny/prophet
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Findings by vulnerability - Vanta
Findings by vulnerability - Vanta
NVD - cve-2026-33671
NVD - cve-2026-33671
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
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-24765</tabTitle>” with “<selection>CVE-2026-24765 Detail Description PHPUnit is a testing framework for PHP. A vulnerability has been discovered in versions prior to 12.5.8, 11.5.50, 10.5.62, 9.6.33, and 8.5.52 involving unsafe deserialization of code coverage data in PHPT test execution. The vulnerability exists in the `cleanupForCoverage()` method, which deserializes code coverage files without validation, potentially allowing remote code execution if malicious `.coverage` files are present prior to the execution of the PHPT test. The vulnerability occurs when a `.coverage` file, which should not exist before test execution, is deserialized without the `allowed_classes` parameter restriction. An attacker with local file write access can place a malicious serialized object with a `__wakeup()` method into the file system, leading to arbitrary code execution during test runs with code coverage instrumentation enabled. This vulnerability requires local file write access to the location where PHPUnit stores or expects code coverage files for PHPT tests. This can occur through CI/CD pipeline attacks, the local development environment, and/or compromised dependencies. Rather than just silently sanitizing the input via `['allowed_classes' => false]`, the maintainer has chosen to make the anomalous state explicit by treating pre-existing `.coverage` files for PHPT tests as an error condition. Starting in versions in versions 12.5.8, 11.5.50, 10.5.62, 9.6.33, when a `.coverage` file is detected for a PHPT test prior to execution, PHPUnit will emit a clear error message identifying the anomalous state. Organizations can reduce the effective risk of this vulnerability through proper CI/CD configuration, including ephemeral runners, code review enforcement, branch protection, artifact isolation, and access control. 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 Base Score: N/A NVD assessment not yet provided. CNA: GitHub, Inc. Base Score: 7.8 HIGH Vector: CVSS:3.1/AV:L/AC:L/PR:L/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/sebastianbergmann/phpunit/commit/3141742e00620e2968d3d2e732d320de76685fda GitHub, Inc. Patch https://github.com/sebastianbergmann/phpunit/releases/tag/10.5.63 GitHub, Inc. Release Notes https://github.com/sebastianbergmann/phpunit/releases/tag/11.5.50 GitHub, Inc. Release Notes https://github.com/sebastianbergmann/phpunit/releases/tag/12.5.8 GitHub, Inc. Release Notes https://github.com/sebastianbergmann/phpunit/releases/tag/8.5.52 GitHub, Inc. Release Notes https://github.com/sebastianbergmann/phpunit/releases/tag/9.6.33 GitHub, Inc. Release Notes https://github.com/sebastianbergmann/phpunit/security/advisories/GHSA-vvj3-c3rp-c85p GitHub, Inc. Mitigation Vendor Advisory https://lists.debian.org/debian-lts-announce/2026/02/msg00009.html CVE Mailing List Third Party Advisory Weakness Enumeration CWE-ID CWE Name Source CWE-502 Deserialization of Untrusted Data GitHub, Inc. Known Affected Software Configurations Switch to CPE 2.2 Configuration 1 ( hide ) cpe:2.3:a:phpunit_project:phpunit:*:*:*:*:*:-:*:* Show Matching CPE(s) Up to (excluding)8.5.52 cpe:2.3:a:phpunit_project:phpunit:*:*:*:*:*:-:*:* Show Matching CPE(s) From (including)9.0.0Up to (excluding)9.6.33 cpe:2.3:a:phpunit_project:phpunit:*:*:*:*:*:-:*:* Show Matching CPE(s) From (including)10.0.0Up to (excluding)10.5.62 cpe:2.3:a:phpunit_project:phpunit:*:*:*:*:*:-:*:* Show Matching CPE(s) From (including)11.0.0Up to (excluding)11.5.50 cpe:2.3:a:phpunit_project:phpunit:*:*:*:*:*:-:*:* Show Matching CPE(s) From (including)12.0.0Up to (excluding)12.5.8 Configuration 2 ( hide ) cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:* Show Matching CPE(s) Denotes Vulnerable Software Are we missing a CPE here? Please let us know. Change History 3 change records found show changes Quick Info CVE Dictionary Entry: CVE-2026-24765 NVD Published Date: 01/27/2026 NVD Last Modified: 03/03/2026 Source: GitHub, Inc.</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-24765</tabTitle>” with “<selection>CVE-2026-24765
Detail
Description
PHPUnit is a testing framework for PHP. A vulnerability has been discovered in versions prior to 12.5.8, 11.5.50, 10.5.62, 9.6.33, and 8.5.52 involving unsafe deserialization of code coverage data in PHPT test execution. The vulnerability exists in the `cleanupForCoverage()` method, which deserializes code coverage files without validation, potentially allowing remote code execution if malicious `.coverage` files are present prior to the execution of the PHPT test. The vulnerability occurs when a `.coverage` file, which should not exist before test execution, is deserialized without the `allowed_classes` parameter restriction. An attacker with local file write access can place a malicious serialized object with a `__wakeup()` method into the file system, leading to arbitrary code execution during test runs with code coverage instrumentation enabled. This vulnerability requires local file write access to the location where PHPUnit stores or expects code coverage files for PHPT tests. This can occur through CI/CD pipeline attacks, the local development environment, and/or compromised dependencies. Rather than just silently sanitizing the input via `['allowed_classes' => false]`, the maintainer has chosen to make the anomalous state explicit by treating pre-existing `.coverage` files for PHPT tests as an error condition. Starting in versions in versions 12.5.8, 11.5.50, 10.5.62, 9.6.33, when a `.coverage` file is detected for a PHPT test prior to execution, PHPUnit will emit a clear error message identifying the anomalous state. Organizations can reduce the effective risk of this vulnerability through proper CI/CD configuration, including ephemeral runners, code review enforcement, branch protection, artifact isolation, and access control.
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
Base
Score: N/A
NVD assessment
not yet provided.
CNA: GitHub, Inc.
Base
Score: 7.8 HIGH
Vector: CVSS:3.1/AV:L/AC:L/PR:L/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/sebastianbergmann/phpunit/commit/3141742e00620e2968d3d2e732d320de76685fda
GitHub, Inc.
Patch
https://github.com/sebastianbergmann/phpunit/releases/tag/10.5.63
GitHub, Inc.
Release Notes
https://github.com/sebastianbergmann/phpunit/releases/tag/11.5.50
GitHub, Inc.
Release Notes
https://github.com/sebastianbergmann/phpunit/releases/tag/12.5.8
GitHub, Inc.
Release Notes
https://github.com/sebastianbergmann/phpunit/releases/tag/8.5.52
GitHub, Inc.
Release Notes
https://github.com/sebastianbergmann/phpunit/releases/tag/9.6.33
GitHub, Inc.
Release Notes
https://github.com/sebastianbergmann/phpunit/security/advisories/GHSA-vvj3-c3rp-c85p
GitHub, Inc.
Mitigation
Vendor Advisory
https://lists.debian.org/debian-lts-announce/2026/02/msg00009.html
CVE
Mailing List
Third Party Advisory
Weakness Enumeration
CWE-ID
CWE Name
Source
CWE-502
Deserialization of Untrusted Data
GitHub, Inc.
Known Affected Software Configurations Switch
to CPE 2.2
Configuration 1 ( hide ) cpe:2.3:a:phpunit_project:phpunit:*:*:*:*:*:-:*:* Show Matching CPE(s)
Up to (excluding)8.5.52 cpe:2.3:a:phpunit_project:phpunit:*:*:*:*:*:-:*:* Show Matching CPE(s)
From (including)9.0.0Up to (excluding)9.6.33 cpe:2.3:a:phpunit_project:phpunit:*:*:*:*:*:-:*:* Show Matching CPE(s)
From (including)10.0.0Up to (excluding)10.5.62 cpe:2.3:a:phpunit_project:phpunit:*:*:*:*:*:-:*:* Show Matching CPE(s)
From (including)11.0.0Up to (excluding)11.5.50 cpe:2.3:a:phpunit_project:phpunit:*:*:*:*:*:-:*:* Show Matching CPE(s)
From (including)12.0.0Up to (excluding)12.5.8 Configuration 2 ( hide ) cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:* Show Matching CPE(s)
Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.
Change History
3 change records found show changes
Quick Info
CVE Dictionary Entry: CVE-2026-24765 NVD
Published Date: 01/27/2026 NVD
Last Modified: 03/03/2026
Source: GitHub, Inc.</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-24765: PHPUnit Insecure Deserialization
Summary of CVE-2026-24765: PHPUnit Insecure Deserialization
CVE-2026-24765 describes a high-severity security vulnerability in
PHPUnit
, a popular testing framework for PHP. The flaw allows for potential
Remote Code Execution (RCE)
through the unsafe handling of code coverage data.
Vulnerability Mechanism
Vulnerability Mechanism
Root Cause:
The
cleanupForCoverage()
method in PHPUnit performs deserialization on
.coverage
files during PHPT test execution without restricting the classes that can be instantiated (lacking the
allowed_classes
parameter).
Attack Vector:
An attacker with local file write access can place a malicious serialized PHP object into a
.coverage
file.
Impact:
When PHPUnit runs tests with code coverage instrumentation enabled, it deserializes the malicious file. If the object contains a
__wakeup()
magic method, it can trigger arbitrary code execution in the context of the user running the tests.
Affected Versions
Affected Versions
The vulnerability impacts versions prior to:
12.x:
Before 12.5.8
11.x:
Before 11.5.50
10.x:
Before 10.5.62
9.x:
Before 9.6.33
8.x:
Before 8.5.52
Risk Assessment
Risk Assessment
CVSS Score:
7.8 (High)
Vector:
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Requirement:
Requires local file write access to the directory where PHPUnit expects coverage files. Common threat environments include compromised CI/CD pipelines, local development machines, or malicious dependencies.
Resolution and Mitigation
Resolution and Mitigation
Official Patch:
The maintainer updated PHPUnit to treat pre-existing...
|
Firefox
|
[JY-19967] Upgrade Python and libraries - Apr - Ji [JY-19967] Upgrade Python and libraries - Apr - Jira — Work...
|
jiminny.atlassian.net/browse/JY-19967?search_id=91 jiminny.atlassian.net/browse/JY-19967?search_id=91e0961a-9652-4c0d-bf2c-016738fc3f74&referrer=quick-find...
|
32748
|
|
32749
|
rirerox(JY-19967] Upgrade Python arDependabot aler rirerox(JY-19967] Upgrade Python arDependabot alerts • jiminny/proph# (UY-19958] Upgrade BE ibraries -Findings by vulnerability - VantaNo NVD - cve-2026-33671Low vulnerabilities identified in paiminnylaop/backend-code - Vanta1o NVD -cve-2026-6722fuy-207731 User Pilot not receivin@ JY-19957 | Remove abanded sympTypeError: Leaque\Flysystem\FilesNew Tabu Userpilot | Ask Jiminny Report Gen(SRD-6848] Sidekick SMS issue. 1Y-199571 Unarade BE librariesJY-19957 | Remove abanded symp2 Hich vulnerabilities identified in oã(* Medium vulnerabilities identified inLow vulnerabilities identified in paWindownva.nist.eovvuln/celall/cve-4040-550/1• Goodle geminiShow thinkingAcsessment. Satebasee on ne ermina ouel volu eroviceevour Laravel prolect is nor vuinerable toCVE-2026-24765.• Your Installed Version: 11.5.55• Secure Patched Version: 11.5.50 (forthe 11.x release branch)Because you are running 11.5.55 , which isnewer than the required security patch, theunsafe deserialization flaw in thecleanupForCoverage() method has alreadybeen resolved in your environment. You don'tneed to take any further action to upgradePHPUnit for this specific CVE.A quick reminder on best practices:Since you are running this inside a Dockercontainer ( docker_1amp_1 ), just ensure thatwhen you build your production containerimages, you continue to use the --no-dev flagwith Composer. This guarantees that PHPUnit isentirely excluded from your live productionenvironmentsEnter a prompt for GeminiAlit can make mistakes, so double check it. Your privacy & GelSummarize pageCNA: GitHub, Inc.Base Score: 7,5 HVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HReferences to Advisories, Solutions, and ToolsBy selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may haveinformation that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from thispage. 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 onthese sites. Please address comments about this page to [EMAIL]://github.com/micromatch/picomatch/commit/5eceecd27543b8e056b9307d69e105ea03618a7d GitHub, Inc.https://github.com/micromatch/picomatch/security/advisories/GHSA-c2c7-rcm5-vajSource(s)GitHub, Inc.Tag(s)PatchPatch (Vendor Advisory)Weakness EnumerationCWE-IDCWE NameCWE-1333Inefficient Regular Expression ComplexitySourceGitHub, Inc.Known Affected Software Configurations Switch to CPE 2.2contiguration 1 nide )XК срe:2.3:a:jonschlinkert:picomatch:*:*:*:*:*:node.js:*:*Show Matching CPE(s)~aE cpe:2.3:a:jonschlinkert:picomatch:*:*:*.*:*:node.js:*:*Show Matching CPE(s)~ЖE cpe:2.3:a:jonschlinkert:picomatch:*:***:*:node.js:*:*Show Matching CPF(s)vUp to (excluding)2.3.2From (including)3.0.0From (including)4.0.0Up to (excluding)3.0.2Up to (excluding)4.0.4JE Denotes Vulnerable SoftwareAre we missing a CPE here? Please let us know.Change History2 change records tound show changedNSTHEADOUARTERSon DuGaithersburg, MD 20899(301) .975-2000Webmaster | Contact Us | Our Other OfficesS0 lihl 1 Support Daily - in 2h 24m(A100% C/ &• Wed 13 May 12:36:09Incident Response Assistance and Non-NVD RelatedPhone: 66 220890...
|
Firefox
|
[JY-19967] Upgrade Python and libraries - Apr - Ji [JY-19967] Upgrade Python and libraries - Apr - Jira — Work...
|
jiminny.atlassian.net/browse/JY-19967?search_id=91 jiminny.atlassian.net/browse/JY-19967?search_id=91e0961a-9652-4c0d-bf2c-016738fc3f74&referrer=quick-find...
|
32749
|
|
32750
|
[JY-19967] Upgrade Python and libraries - Apr - Ji [JY-19967] Upgrade Python and libraries - Apr - Jira
[JY-19967] Upgrade Python and libraries - Apr - Jira
Close tab
Dependabot alerts · jiminny/prophet
Dependabot alerts · jiminny/prophet
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Findings by vulnerability - Vanta
Findings by vulnerability - Vanta
NVD - cve-2026-33671
NVD - cve-2026-33671
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
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-24765</tabTitle>” with “<selection>CVE-2026-24765 Detail Description PHPUnit is a testing framework for PHP. A vulnerability has been discovered in versions prior to 12.5.8, 11.5.50, 10.5.62, 9.6.33, and 8.5.52 involving unsafe deserialization of code coverage data in PHPT test execution. The vulnerability exists in the `cleanupForCoverage()` method, which deserializes code coverage files without validation, potentially allowing remote code execution if malicious `.coverage` files are present prior to the execution of the PHPT test. The vulnerability occurs when a `.coverage` file, which should not exist before test execution, is deserialized without the `allowed_classes` parameter restriction. An attacker with local file write access can place a malicious serialized object with a `__wakeup()` method into the file system, leading to arbitrary code execution during test runs with code coverage instrumentation enabled. This vulnerability requires local file write access to the location where PHPUnit stores or expects code coverage files for PHPT tests. This can occur through CI/CD pipeline attacks, the local development environment, and/or compromised dependencies. Rather than just silently sanitizing the input via `['allowed_classes' => false]`, the maintainer has chosen to make the anomalous state explicit by treating pre-existing `.coverage` files for PHPT tests as an error condition. Starting in versions in versions 12.5.8, 11.5.50, 10.5.62, 9.6.33, when a `.coverage` file is detected for a PHPT test prior to execution, PHPUnit will emit a clear error message identifying the anomalous state. Organizations can reduce the effective risk of this vulnerability through proper CI/CD configuration, including ephemeral runners, code review enforcement, branch protection, artifact isolation, and access control. 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 Base Score: N/A NVD assessment not yet provided. CNA: GitHub, Inc. Base Score: 7.8 HIGH Vector: CVSS:3.1/AV:L/AC:L/PR:L/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) [URL_WITH_CREDENTIALS] composer show phpunit/phpunit name : phpunit/phpunit descrip. : The PHP Unit Testing framework. keywords : phpunit, testing, xunit versions : * 11.5.55 type : library license : BSD 3-Clause "New" or "Revised" License (BSD-3-Clause) (OSI approved) [URL_WITH_CREDENTIALS] composer show phpunit/phpunit
name : phpunit/phpunit
descrip. : The PHP Unit Testing framework.
keywords : phpunit, testing, xunit
versions : * 11.5.55
type : library
license : BSD 3-Clause "New" or "Revised" License (BSD-3-Clause) (OSI approved) https://spdx.org/licenses/BSD-3-Clause.html#licenseText
homepage : https://phpunit.de/
source : [git] https://github.com/sebastianbergmann/phpunit.git adc7262fccc12de2b30f12a8aa0b33775d814f00
dist : [zip] https://api.github.com/repos/sebastianbergmann/phpunit/zipball/adc7262fccc12de2b30f12a8aa0b33775d814f00 adc7262fccc12de2b30f12a8aa0b33775d814f00
path : /home/jiminny/vendor/phpunit/phpunit
names : phpunit/phpunit
support
issues : https://github.com/sebastianbergmann/phpunit/issues
security : https://github.com/sebastianbergmann/phpunit/security/policy
source : https://github.com/sebastianbergmann/phpunit/tree/11.5.55
autoload
files
classmap
src/
requires
ext-dom *
ext-json *
ext-libxml *
ext-mbstring *
ext-xml *
ext-xmlwriter *
myclabs/deep-copy ^1.13.4
phar-io/manifest ^2.0.4
phar-io/version ^3.2.1
php >=8.2
phpunit/php-code-coverage ^11.0.12
phpunit/php-file-iterator ^5.1.1
phpunit/php-invoker ^5.0.1
phpunit/php-text-template ^4.0.1
phpunit/php-timer ^7.0.1
sebastian/cli-parser ^3.0.2
sebastian/code-unit ^3.0.3
sebastian/comparator ^6.3.3
sebastian/diff ^6.0.2
sebastian/environment ^7.2.1
sebastian/exporter ^6.3.2
sebastian/global-state ^7.0.2
sebastian/object-enumerator ^6.0.1
sebastian/recursion-context ^6.0.3
sebastian/type ^5.1.3
sebastian/version ^5.0.2
staabm/side-effects-detector ^1.0.5
suggests
ext-soap To be able to generate mocks based on WSDL files
Expand
Listen
Show thinking
Gemini said
Gemini said
Assessment: Safe
Assessment: Safe
Based on the terminal output you provided, your Laravel project is
not vulnerable
to CVE-2026-24765.
Your Installed Version:
11.5.55
Secure Patched Version:
11.5.50
(for the 11.x release branch)
Because you are running
11.5.55
, which is newer than the required security patch, the unsafe deserialization flaw in the
cleanupForCoverage()
method has already been resolved in your environment. You don't need to take any further action to upgrade PHPUnit for this specific CVE.
A quick reminder on best practices:
Since you are running this inside a Docker container (
docker_lamp_1
), just ensure that when you build your production container images, you continue to use the...
|
Firefox
|
[JY-19967] Upgrade Python and libraries - Apr - Ji [JY-19967] Upgrade Python and libraries - Apr - Jira — Work...
|
jiminny.atlassian.net/browse/JY-19967?search_id=91 jiminny.atlassian.net/browse/JY-19967?search_id=91e0961a-9652-4c0d-bf2c-016738fc3f74&referrer=quick-find...
|
32750
|
|
32381
|
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...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/browse/JY-19965?search_id=f8 jiminny.atlassian.net/browse/JY-19965?search_id=f879fe0d-a07a-47c3-b2e7-d9660ca59305&referrer=quick-find...
|
32381
|
|
32382
|
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...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/browse/JY-19965?search_id=f8 jiminny.atlassian.net/browse/JY-19965?search_id=f879fe0d-a07a-47c3-b2e7-d9660ca59305&referrer=quick-find...
|
32382
|
|
32383
|
[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:
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
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
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
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]...
|
Firefox
|
[JY-19965] Upgrade BE libraries - Dec - Jira — Wor [JY-19965] Upgrade BE libraries - Dec - Jira — Work...
|
jiminny.atlassian.net/browse/JY-19965?search_id=f8 jiminny.atlassian.net/browse/JY-19965?search_id=f879fe0d-a07a-47c3-b2e7-d9660ca59305&referrer=quick-find...
|
32383
|
|
30282
|
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
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
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...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/browse/JY-19958
|
30282
|
|
30283
|
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
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
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...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/browse/JY-19958
|
30283
|
|
30284
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Jira
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)
Transferring data from jiminny.atlassian.net…...
|
Firefox
|
Jira — Work
|
jiminny.atlassian.net/browse/JY-19958
|
30284
|
|
30285
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Jira
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)
Transferring data from jiminny.atlassian.net…...
|
Firefox
|
Jira — Work
|
jiminny.atlassian.net/browse/JY-19958
|
30285
|
|
30286
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Jira
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:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
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
Board actions
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
Assets , (opens new window)
Assets
, (opens new window)
open menu
open menu
Customise sidebar
Customise sidebar
Resize side navigation panel
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-12249
JY-12249
/
Technical Story - Change work type
JY-19958
JY-19958
Copy link
Upgrade BE libraries - May- Summary, edit
Upgrade BE libraries - May
Upgrade BE libraries - May
Add or create work related to this Technical Story
Add or create work related to this Technical Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Add Description, edit
Fix BE vulnerabilities:
https://app.vanta.com/c/jiminny.com/vulnerabilities/findings-by-asset/672dbbd0b16e6beaba3ddc4f
https://app.vanta.com/c/jiminny.com/vulnerabilities/findings-by-asset/672dbbd0b16e6beaba3ddc4f
https://app.vanta.com/c/jiminny.com/tests/packages-checked-for-vulnerabilities-v2-records-closed-github-dependabot-high?tab=results
https://app.vanta.com/c/jiminny.com/tests/packages-checked-for-vulnerabilities-v2-records-closed-github-dependabot-high?tab=results
https://app.vanta.com/c/jiminny.com/tests/packages-checked-for-vulnerabilities-v2-records-closed-github-dependabot-medium?tab=results
https://app.vanta.com/c/jiminny.com/tests/packages-checked-for-vulnerabilities-v2-records-closed-github-dependabot-medium?tab=results
https://app.vanta.com/c/jiminny.com/tests/packages-checked-for-vulnerabilities-v2-records-closed-github-dependabot-low?tab=results
https://app.vanta.com/c/jiminny.com/tests/packages-checked-for-vulnerabilities-v2-records-closed-github-dependabot-low?tab=results
Subtasks
Subtasks
Add subtask
Add subtask
Linked work items
Linked work items
Add linked work item
Add linked work item
Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Newest first Newest first
Newest first
Add a comment…
Status update...
Status update...
Thanks...
Thanks...
Agree...
Agree...
Pro tip:...
|
Firefox
|
Jira — Work
|
jiminny.atlassian.net/browse/JY-19958
|
30286
|
|
30287
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Jira
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:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
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
Board actions
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
Assets , (opens new window)
Assets
, (opens new window)
open menu
open menu
Customise sidebar
Customise sidebar
Resize side navigation panel
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-12249
JY-12249
/
Technical Story - Change work type
JY-19958
JY-19958
Copy link
Upgrade BE libraries - May- Summary, edit
Upgrade BE libraries - May
Upgrade BE libraries - May
Add or create work related to this Technical Story
Add or create work related to this Technical Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Add Description, edit
Fix BE vulnerabilities:
https://app.vanta.com/c/jiminny.com/vulnerabilities/findings-by-asset/672dbbd0b16e6beaba3ddc4f
https://app.vanta.com/c/jiminny.com/vulnerabilities/findings-by-asset/672dbbd0b16e6beaba3ddc4f
https://app.vanta.com/c/jiminny.com/tests/packages-checked-for-vulnerabilities-v2-records-closed-github-dependabot-high?tab=results
https://app.vanta.com/c/jiminny.com/tests/packages-checked-for-vulnerabilities-v2-records-closed-github-dependabot-high?tab=results
https://app.vanta.com/c/jiminny.com/tests/packages-checked-for-vulnerabilities-v2-records-closed-github-dependabot-medium?tab=results
https://app.vanta.com/c/jiminny.com/tests/packages-checked-for-vulnerabilities-v2-records-closed-github-dependabot-medium?tab=results
https://app.vanta.com/c/jiminny.com/tests/packages-checked-for-vulnerabilities-v2-records-closed-github-dependabot-low?tab=results
https://app.vanta.com/c/jiminny.com/tests/packages-checked-for-vulnerabilities-v2-records-closed-github-dependabot-low?tab=results
Subtasks
Subtasks
Add subtask
Add subtask
Linked work items
Linked work items
Add linked work item
Add linked work item
Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Newest first Newest first
Newest first
Add a comment…
Status update...
Status update...
Thanks...
Thanks...
Agree...
Agree...
Pro tip:
press
M
to comment
Resize work item view side panel
Watch options: You are not watching this issue, 1 person watching
1
Share
Share
Actions
Actions
Backlog - Change status
Backlog
Automation
Automation...
|
Firefox
|
Jira — Work
|
jiminny.atlassian.net/browse/JY-19958
|
30287
|
|
30288
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - 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:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
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
Board actions
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)
Jiminny (New)
/
Epic - Change parent
JY-12249
JY-12249
/
Technical Story - Change work type
JY-19958
JY-19958
Copy link
Upgrade BE libraries - May- Summary, edit
Upgrade BE libraries - May
Upgrade BE libraries - May
Add or create work related to this Technical Story
Add or create work related to this Technical Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Fix BE vulnerabilities:
Vanta
Vanta
Vanta
Vanta
Vanta...
|
Firefox
|
[JY-19958] Upgrade BE libraries - May - Jira — Wor [JY-19958] Upgrade BE libraries - May - Jira — Work...
|
jiminny.atlassian.net/browse/JY-19958
|
30288
|
|
30289
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - 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:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
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
Board actions
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...
|
Firefox
|
[JY-19958] Upgrade BE libraries - May - Jira — Wor [JY-19958] Upgrade BE libraries - May - Jira — Work...
|
jiminny.atlassian.net/browse/JY-19958
|
30289
|
|
30298
|
[JY-19958] Upgrade BE libraries - May - Jira
jimin [JY-19958] Upgrade BE libraries - May - Jira
jiminny.atlassian.net
Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Close tab
Vanta
Vanta
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:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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...
|
Firefox
|
Vanta — Work
|
jiminny.atlassian.net/browse/JY-19958
|
30298
|
|
30299
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Close tab
Vanta
Vanta
[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:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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...
|
Firefox
|
[JY-19958] Upgrade BE libraries - May - Jira — Wor [JY-19958] Upgrade BE libraries - May - Jira — Work...
|
jiminny.atlassian.net/browse/JY-19958
|
30299
|
|
30300
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Close tab
Vanta
Vanta
[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:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
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
Board actions
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)
Jiminny (New)
/
Epic - Change parent
JY-12249
JY-12249
/
Technical Story - Change work type
JY-19958
JY-19958
Copy link
Upgrade BE libraries - May- Summary, edit
Upgrade BE libraries - May
Upgrade BE libraries - May
Add or create work related to this Technical Story
Add or create work related to this Technical Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Fix BE vulnerabilities:
Vanta
Vanta
Vanta
Vanta
Vanta
Vanta
Vanta
Vanta
Subtasks
Subtasks
Add subtask
Add subtask
Linked work items
Linked work items
Add linked work item
Add linked work item
Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Newest first Newest first
Newest first
Add a comment…
Status update...
Status update...
Thanks...
Thanks...
Agree...
Agree...
Pro tip:
press
M
to comment
Resize work item view side panel
Watch options: You are not watching this issue, 1 person watching
1
Share
Share
Actions...
|
Firefox
|
[JY-19958] Upgrade BE libraries - May - Jira — Wor [JY-19958] Upgrade BE libraries - May - Jira — Work...
|
jiminny.atlassian.net/browse/JY-19958
|
30300
|
|
30301
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Close tab
Vanta
Vanta
[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:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
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
Board actions
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)
Jiminny (New)
/
Epic - Change parent
JY-12249
JY-12249
/
Technical Story - Change work type
JY-19958
JY-19958
Copy link
Upgrade BE libraries - May- Summary, edit
Upgrade BE libraries - May
Upgrade BE libraries - May
Add or create work related to this Technical Story
Add or create work related to this Technical Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Fix BE vulnerabilities:
Vanta
Vanta
Vanta
Vanta
Vanta
Vanta
Vanta
Vanta
Subtasks
Subtasks
Add subtask
Add subtask
Linked work items
Linked work items
Add linked work item
Add linked work item
Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Newest first Newest first
Newest first
Add a comment…
Status update...
Status update...
Thanks...
Thanks...
Agree...
Agree...
Pro tip:
press
M
to comment
Resize work item view side panel
Watch options: You are not watching this issue, 1 person watching
1
Share
Share
Actions
Actions
Backlog - Change status
Backlog
Automation
Automation
Improve Technical Story
Improve Technical Story
Details
Details
Details
Assignee
Assignee Pin to top. Only you can see pinned fields.
Lukas Kovalik- edit Assignee
More information about Lukas Kovalik
Lukas Kovalik
Reporter
Reporter Pin to top. Only you can see pinned fields.
Stefka Stoyanova- edit Reporter
More information about Stefka Stoyanova
Stefka Stoyanova
Development
Development Pin to top. Only you can see pinned fields.
Open with VS Code Link to external website in new tab
Open with VS Code
Create branch Link to external website in new tab
Create branch
Create and checkout new branch
Create commit
Create commit
Components
Components Pin to top. Only you can see pinned fields.
Edit Components, edit
Platform
Platform
Sub-Product
Sub-Product Pin to top. Only you can see pinned fields.
Edit Sub-Product, Add options selected, edit
Add options
Labels
Labels Pin to top. Only you can see pinned fields.
Edit Labels...
|
Firefox
|
[JY-19958] Upgrade BE libraries - May - Jira — Wor [JY-19958] Upgrade BE libraries - May - Jira — Work...
|
jiminny.atlassian.net/browse/JY-19958
|
30301
|
|
30302
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Close tab
Vanta
Vanta
[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:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
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
Board actions
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)
Jiminny (New)
/
Epic - Change parent
JY-12249
JY-12249
/
Technical Story - Change work type
JY-19958
JY-19958
Copy link
Upgrade BE libraries - May- Summary, edit
Upgrade BE libraries - May
Upgrade BE libraries - May
Add or create work related to this Technical Story
Add or create work related to this Technical Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Fix BE vulnerabilities:
Vanta
Vanta
Vanta
Vanta
Vanta
Vanta
Vanta
Vanta
Subtasks
Subtasks
Add subtask
Add subtask
Linked work items
Linked work items
Add linked work item
Add linked work item
Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Newest first Newest first
Newest first
Add a comment…
Status update...
Status update...
Thanks...
Thanks...
Agree...
Agree...
Pro tip:
press
M
to comment
Resize work item view side panel
Watch options: You are not watching this issue, 1 person watching
1
Share
Share
Actions
Actions
Backlog - Change status
Backlog
Automation
Automation
Improve Technical Story
Improve Technical Story
Details
Details
Details
Assignee
Assignee Pin to top. Only you can see pinned fields.
Lukas Kovalik- edit Assignee
More information about Lukas Kovalik
Lukas Kovalik
Reporter
Reporter Pin to top. Only you can see pinned fields.
Stefka Stoyanova- edit Reporter
More information about Stefka Stoyanova...
|
Firefox
|
[JY-19958] Upgrade BE libraries - May - Jira — Wor [JY-19958] Upgrade BE libraries - May - Jira — Work...
|
jiminny.atlassian.net/browse/JY-19958
|
30302
|
|
30303
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Close tab
Vanta
Vanta
[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:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
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
Board actions
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)
Jiminny (New)
/
Epic - Change parent
JY-12249
JY-12249
/
Technical Story - Change work type
JY-19958
JY-19958
Copy link
Upgrade BE libraries - May- Summary, edit
Upgrade BE libraries - May
Upgrade BE libraries - May
Add or create work related to this Technical Story
Add or create work related to this Technical Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Fix BE vulnerabilities:
Vanta
Vanta
Vanta
Vanta
Vanta
Vanta
Vanta
Vanta
Subtasks
Subtasks
Add subtask
Add subtask
Linked work items
Linked work items
Add linked work item
Add linked work item
Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Newest first Newest first
Newest first
Add a comment…
Status update...
Status update...
Thanks...
Thanks...
Agree...
Agree...
Pro tip:
press
M
to comment
Resize work item view side panel
Watch options: You are not watching this issue, 1 person watching
1
Share
Share
Actions
Actions
Backlog - Change status
Backlog
Automation
Automation
Improve Technical Story
Improve Technical Story
Details
Details
Details
Assignee
Assignee Pin to top. Only you can see pinned fields.
Lukas Kovalik- edit Assignee
More information about Lukas Kovalik...
|
Firefox
|
[JY-19958] Upgrade BE libraries - May - Jira — Wor [JY-19958] Upgrade BE libraries - May - Jira — Work...
|
jiminny.atlassian.net/browse/JY-19958
|
30303
|
|
30304
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Close tab
Vanta
Vanta
[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:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
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
Board actions
SE Kanban...
|
Firefox
|
[JY-19958] Upgrade BE libraries - May - Jira — Wor [JY-19958] Upgrade BE libraries - May - Jira — Work...
|
jiminny.atlassian.net/browse/JY-19958
|
30304
|
|
30305
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Close tab
Vanta
Vanta
[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:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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)
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
Board actions
SE Kanban...
|
Firefox
|
[JY-19958] Upgrade BE libraries - May - Jira — Wor [JY-19958] Upgrade BE libraries - May - Jira — Work...
|
jiminny.atlassian.net/browse/JY-19958
|
30305
|
|
30748
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Close tab
Request access to systems - Vanta
Request access to systems - Vanta
[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
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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...
|
Firefox
|
[JY-19958] Upgrade BE libraries - May - Jira — Wor [JY-19958] Upgrade BE libraries - May - Jira — Work...
|
jiminny.atlassian.net/browse/JY-19958
|
30748
|
|
30749
|
Platform Team - Backlog - Jira
Platform Team - Bac Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
[JY-19958] Upgrade BE libraries - May - Jira
[JY-19958] Upgrade BE libraries - May - Jira
Close tab
Request access to systems - Vanta
Request access to systems - Vanta
[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
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
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...
|
Firefox
|
[JY-19958] Upgrade BE libraries - May - Jira — Wor [JY-19958] Upgrade BE libraries - May - Jira — Work...
|
jiminny.atlassian.net/browse/JY-19958
|
30749
|