Client: CredAxis · Fintech & Payments · UK SME lending platform (95 staff)

Reducing Vulnerabilities on a Lending Platform

By TechSupport Team. Published November 16, 2026. Updated .

TechSupport Team maintained CredAxis’ Java lending platform ahead of an audit. Over six months, the client’s Snyk records show critical and high CVEs falling from 33 to 5. Recurring defects fell from 24 to 7 per quarter in Jira.

Client and engagement facts

Client
CredAxis
Industry
Fintech & Payments
Business context
UK SME lending platform (95 staff)
Delivery model
Software maintenance
Application
SME lending platform with decision API
Supplied geography
UK
Company size in source
95 staff

Application stack and tools

Application stack

  • Java 11→17
  • Spring Boot
  • PostgreSQL
  • AWS

Tools used

  • Jira
  • Snyk
  • Datadog
  • web application firewall

Why Support Was Needed

The client needed evidence that linked each change ticket to a pull request, a deployment and a verification check. The work paired dependency updates and code repairs with that record.

Technical Work

  • Linked tickets to reviewed pull requests, deploy records and post-deploy checks.
  • Prioritized vulnerability remediation, starting with two publicly known issues.
  • Repaired the rounding in loan decisions and added a regression test.

Representative Incident

An issue in a credit-bureau SDK had no upstream patch. The team added a web application firewall rule for the known path and documented the residual risk in the audit trail.

Results and how they were measured

Reported results and their measurement scope
MetricBaselineResultUnitsMeasurement windowSource and scope
Recurring defects24/q7/q/q6 monthsClient Jira
Critical/high CVEs3356 monthsClient Snyk
Decision API P951.9 s620 msBaseline: s; Result: ms6 monthsClient Datadog

Evidence and Limitations

Two vendor SDK CVEs were recorded as accepted risks with compensating controls. The table reports the platform’s measures over six months.

Vendor Vulnerability Handling

The team recorded compensating controls and documented accepted risks from unpatched vendor dependencies in the audit trail.

Scope a Similar Engagement

Share the dependencies, recurring defects and release evidence your maintenance work must cover. Request a support plan or explore software maintenance.

Get a technical support plan

Tell us which application needs support, what is reaching your engineers and when you need coverage. TechSupport Team will review the fit and explain the next scoping step.

  • We reply by email.
  • We agree a call about the roles, your stack and the hours.
  • If there is a fit, we propose engineers after an assessment.

A short outline is enough. Add your stack and coverage hours if you know them. Do not include credentials or customer data.

Add coverage and team details

We use these details only to reply to you. Describe the application, stack and hours you need covered. Keep credentials and sensitive technical data out of this form. We save the brief for delivery and use Telegram to notify our team.